Techniques for predictive power management of a mobile device

ABSTRACT

Techniques for managing discussion sharing on a mobile platform, comprising a power application. The power application may include, among other components, a power monitoring component to monitor at least one component and/or at least one application of a mobile device to determine device profile information, and a power management component to provide the determined device profile information of a mobile device to a server device and receive predicted information representative of forecasted power utilization of the mobile device and/or context sensitive recommendation information representative of one or more context sensitive recommendations for the mobile device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/550,007 filed Nov. 21, 2014 and entitled “Techniques for PredictivePower Management of a Mobile Device,” the contents of which is hereinincorporated by reference.

BACKGROUND

A mobile device, such as a mobile smart phone, provides their users witha multimedia content rich experience while away from home and improvestheir users' daily productivity and efficiency while at work. However,many mobile devices have a limited battery life and charging the mobiledevices when battery is low may be inconvenient and/or may even beimpossible. With increased use of mobile devices and increaseddependency of the mobile devices by their users, there is a need for abetter management of battery life on mobile devices.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some novel embodiments described herein. This summaryis not an extensive overview, and it is not intended to identifykey/critical elements or to delineate the scope thereof. Its solepurpose is to present some concepts in a simplified form as a prelude tothe more detailed description that is presented later.

Various embodiments are generally directed to techniques for managingdiscussion sharing on a mobile platform. Some embodiments areparticularly directed to techniques for managing discussion sharingbetween and among one or more power applications on one or more mobiledevices. In one embodiment, for example, an apparatus may include aprocessor circuit, and memory operatively coupled to the processorcircuit. The memory may store the mobile power application for executionby the processor circuit, where the mobile power application mayinclude, among other components, a power monitoring component to monitorat least one component and/or at least one application of a mobiledevice to determine device profile information, and a power managementcomponent to provide the determined device profile information of amobile device to a server device and receive predicted informationrepresentative of forecasted power utilization of the mobile deviceand/or context sensitive recommendation information representative ofone or more context sensitive recommendations for the mobile device.Other embodiments are described and claimed.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative of the various ways in which the principles disclosed hereincan be practiced and all aspects and equivalents thereof are intended tobe within the scope of the claimed subject matter. Other advantages andnovel features will become apparent from the following detaileddescription when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an exemplary embodiment of a predictive powermanagement system.

FIG. 1B illustrates an exemplary embodiment of a device, which may be amobile device, comprising one or more applications.

FIG. 1C illustrates an exemplary embodiment of the mobile powerapplication for managing power utilization of a mobile device.

FIG. 2 illustrates an exemplary embodiment of determining predictedinformation and/or recommendation information.

FIG. 3A illustrates exemplary embodiment of past power curveinformation.

FIG. 3B illustrates exemplary embodiment of past context information.

FIG. 3C illustrates exemplary embodiment of analytics information.

FIG. 3D illustrates a first exemplary operating environment of predictedinformation and/or recommendation information.

FIG. 3E illustrates a second exemplary operating environment ofpredicted information and/or recommendation information.

FIG. 3F illustrates a third exemplary operating environment of predictedinformation and/or recommendation information.

FIG. 4A illustrates one embodiment of a logic flow.

FIG. 4B illustrates another embodiment of a logic flow.

FIG. 5 illustrates an exemplary embodiment of a computing architecture.

DETAILED DESCRIPTION

Various embodiments are generally directed to a mobile power managementsystem to provide predictive power management and context sensitiverecommendations for one or more devices (e.g., one or more mobiledevices, etc.) having a finite capacity of reserved power (e.g., batterypower, etc.) before requiring to replenish the power reserve (e.g.,charge the mobile device, etc.). Typically, most device power managementsystems provide an estimated run time based substantially on current orinstantaneous power use of a device, and typically do not take intoconsideration of aggregate usage patterns of the devices by their users.By aggregating usage patterns of the devices, the predictive powermanagement system may provide context sensitive recommendations for theuser and/or mobile device to, terminate, configure, and/or modify one ormore components and/or applications of the device in order to increasethe power reserve of the mobile device.

To achieve these goals and other improvements, the power applicationexecuting on the mobile device may be generally arranged to capture,store, and/or provide, periodically, the device profile informationrepresentative of power utilization and usage patterns of one or moreapplications and/or components of the mobile device, such as, forexample, one or more applications executing in foreground, background,and/or suspended state, one or more components such as the processingcomponent (central processing unit, graphics processing unit, etc.),storage component (e.g., flash memory, hard disks, etc.), system memory(e.g., random access memory, etc.), communications component (e.g.,Wi-Fi, Bluetooth, Cellular, etc.), touch sensitive display component(e.g., display screen, etc.), location component (e.g., globalpositioning system etc.), acceleration component (e.g., accelerometer,etc.), audio input/output component (e.g., speakers, microphones etc.).Additionally, the power application may also be generally arranged tocapture and/or store, periodically calendar events associated with thecalendar application of mobile device as part of the device profileinformation. Optionally, the power application may also be arranged tocapture and/or store at least a portion of the user profile information(e.g., social events and demographic information, etc.) associated witha social networking system. To reduce power utilization of the mobilepower application in predicting power utilization, the device profileinformation and/or the user profile information may be provided,periodically, to a power analytics application which may be implementedon a server device as part of a cloud computing platform.

Based at least partially on the captured and/or stored device profileinformation and optionally, the user profile information captured and/orstored, the power analytics application may generate past contextinformation representative of past activities or past contexts that theuser of the mobile device and/or the mobile device itself may haveperformed in the past. The power analytics application may alsodetermine past application context information during each of the pastactivities or past contexts representative of the applications that wereexecuted during those past activities or past contexts. The poweranalytics application may further determine past power curve informationrepresentative of past power utilization during the one or more pastactivities or past contexts.

Based at least partially on the device profile information, the pastcontext information, past power curve information, and/or the userprofile information for a recurring day of the week (e.g., every Mondayin the past 12 weeks, every Tuesday in the past 4 weeks, etc.), thepower analytics application, utilizing machine learning techniques, maydetermine analytics context information representative of estimated orforecasted activities or analytics contexts (e.g., meetings, traveling,work, home, etc.) for that recurring day of the week (e.g., Mondays,etc.) that the user of the mobile device and/or the mobile device itselfmay perform. The power analytics application may also determineanalytics application context information during each of the estimatedor forecasted activities or analytics contexts representative of theapplications that are likely to be executed during the estimated orforecasted activities or analytics contexts. The power analyticsapplication may further determine the estimated or forecasted powerutilization during each of the estimated or forecasted activities oranalytics contexts for a reoccurring day of the week (e.g., Monday,Tuesday, etc.).

Based at least partially on the device profile information (e.g.,calendar events, etc.) and/or user profile information, the poweranalytics application may determine future context informationrepresentative of one or more scheduled, planned, or otherwiseanticipated activities or future contexts. The power analyticsapplication may also determine future application context informationduring each of the scheduled, planned, or otherwise anticipatedactivities or future contexts representative of the applications thatare likely to be executed during those scheduled, planned, or otherwiseanticipated activities or future contexts. The power analyticsapplication may also determine future power curve informationrepresentative of an estimated or anticipated power utilization duringthose activities scheduled, planned, or otherwise anticipatedactivities.

Based at least partially on the future context information, future powercurve information, future application context information, past contextinformation, past power curve information, past application contextinformation, analytics power curve information, analytics contextinformation, and/or analytics application context information, the poweranalytics application may determine predicted context informationrepresentative of the past activities or past contexts that has alreadybeen performed, the future activates or contexts that will be performed,and/or the estimated or forecasted activities or analytics contexts thatis likely to be performed on a reoccurring day of the week (e.g., aMonday, etc.). The power analytics application may also determinepredicted power curve information representative of the powerutilization for each of the contexts represented by predicted contextinformation. Based at least partially on the predicted contextinformation and predicted power curve information, the power analyticsapplication may further determine predicted power event informationwhich may provide the estimated time the battery of the mobile devicemay fall below a predetermined threshold level (e.g., less than 5% powerremaining, etc.) and estimated or forecasted time the user typicallycharges the mobile device.

Based at least partially on the predicted power event information andpredicted context information, power analytics application may furtherdetermine that based on the past power utilization represented by pastpower curve information, the scheduled, planned or anticipated powerutilization, and/or estimated or forecasted power utilization, mobiledevice may be unable to be utilized for one or more the scheduled,planned or anticipated activities and/or estimated or forecastedactivities (e.g., recording audio for meetings, providing GPS navigationduring traveling, sending and/or receiving emails while at work, etc.).As such, based at least partially on the predicted power eventinformation, the predicted context information, and/or predicted powercurve information, the power analytics application may generate one ormore context sensitive recommendations represented by context sensitiverecommendation information for one or more activities or contexts toreduce power utilization while retaining at least some functionality ofthe mobile device during the one or more activities or contexts.

It may be appreciated that because the predicted power curve informationand/or predicted context information are determined based on powerutilization and activities or contexts accrued for several reoccurringdays of the week (e.g., one or more Mondays for 12 weeks, etc.), thepredicted power utilization may adapt over time to a mobile device'spower utilization patterns for one or more recurring day of the week(e.g., Monday, Tuesday, etc.) and provide context sensitiverecommendations that take into consideration expected power utilization(e.g., expected execution of one or more applications on the mobiledevice throughout a reoccurring day of the week).

As a result of these improvements discussed above and elsewhere, theuser's experiences and expectations of power utilization on a mobiledevice may be greatly improved.

With general reference to notations and nomenclature used herein, thedetailed descriptions which follow may be presented in terms of programprocedures executed on a computer or network of computers. Theseprocedural descriptions and representations are used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art.

A procedure is here, and generally, conceived to be a self-consistentsequence of operations leading to a desired result. These operations arethose requiring physical manipulations of physical quantities. Usually,though not necessarily, these quantities take the form of electrical,magnetic or optical signals capable of being stored, transferred,combined, compared, and otherwise manipulated. It proves convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, values, elements, symbols, characters, terms, numbers,or the like. It should be noted, however, that all of these and similarterms are to be associated with the appropriate physical quantities andare merely convenient labels applied to those quantities.

Further, the manipulations performed are often referred to in terms,such as adding or comparing, which are commonly associated with mentaloperations performed by a human operator. No such capability of a humanoperator is necessary, or desirable in most cases, in any of theoperations described herein which form part of one or more embodiments.Rather, the operations are machine operations. Useful machines forperforming operations of various embodiments include general purposedigital computers or similar devices.

Various embodiments also relate to apparatus or systems for performingthese operations. This apparatus may be specially constructed for theneeded purpose or it may comprise a general purpose computer asselectively activated or reconfigured by a computer program stored inthe computer. The procedures presented herein are not inherently relatedto a particular computer or other apparatus. Various general purposemachines may be used with programs written in accordance with theteachings herein, or it may prove convenient to construct morespecialized apparatus to perform the needed method steps. The neededstructure for a variety of these machines will appear from thedescription given.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding thereof. It maybe evident, however, that the novel embodiments can be practiced withoutthese specific details. In other instances, well known structures anddevices are shown in block diagram form in order to facilitate adescription thereof. The intention is to cover all modifications,equivalents, and alternatives consistent with the claimed subjectmatter.

FIG. 1A illustrates an exemplary embodiment of a predictive powermanagement system 100. In various embodiments, the predictive powermanagement system 100 may comprise a social networking system 101 (e.g.,Facebook®, Google+®, LinkedIn®, etc.), a power analytics system 105, andone or more devices 102-a (e.g., server devices, devices, computingdevices, networking devices, etc.). In some embodiments, the one or moredevices 102-a may provide power analytics services to enable varioususers (e.g., persons, businesses, hardware/software components,computing devices, etc.) and/or their devices to manage powerutilization based at least partially on one or more context sensitiverecommendations. In some embodiments, the one or more devices 102-a mayalso provide social networking services to enable various users tocommunicate and interact between and among each other. To provide thepower analytics services and/or social networking services to varioususers, the one or more devices 102-a associated with various users mayalso be operatively coupled to the social networking system 101 viacommunications network 103 (e.g., internet, intranet, cellular network,etc.) utilizing various communications mediums (e.g., wired, wireless,fiber optic, etc.) and/or communications standards (e.g., Ethernet IEEE802.3, Wireless IEEE 802.11, WiMAX IEEE 802.16, Global Systems forMobile Communications (GSM), Enhanced Data Rates for GSM Evolution(EDGE), Long Term Evolution (LTE), etc.).

It is worthy to note that “a” and “b” and “c” and similar designators asused herein are intended to be variables representing any positiveinteger. Thus, for example, if an implementation sets a value for a=2,then a complete set of devices 102-a may include devices 102-1 and102-2. Similarly, if an implementation sets value for a=2, then acomplete set of applications 124-a-1 may include applications 124-1-1and 124-2-1. Furthermore, if an implementation sets value for b=7, thena complete set of applications 124-1-b may include applications 124-1-1,124-1-2, 124-1-3, 124-1-4, 124-1-5, 124-1-6, and 124-1-7. Theembodiments are not limited in this context.

To utilize the power analytics services provided by the power analyticssystem 105, each device of the one or more devices 102-a may beconfigured to execute at least applications 124-a-1. The applications124-a-1 may be configured to communicate with the power analytics system105 and/or social networking system 101 via communications network 103to provide the power analytics services to the users. To enable thepower analytics system 105 to provide aggregate context sensitiverecommendations, each user of applications 124-a-1 may also beassociated with a user account in the social networking system 101. Eachuser account may be represented by user account information. The useraccount information for each user may include, but is not limited to,user account identifier (e.g., phone number, e-mail address, etc.), useraccount authentication token (e.g., user account password, physicaland/or virtual security tokens, etc.), and/or any other informationrelevant to the authentication and authorization of each user. To ensureauthorized access of each user, the social networking system 101 may befurther configured to authenticate each user based on at least a portionof the user account information (e.g., user account identifier, useraccount authentication token, etc.) provide by each user and receivedfrom one or more devices 102-a. Once a user having the associated useraccount has been successfully authenticated, the social networkingsystem 101 may provide one or more applications (e.g., application124-1-1, etc.) with one or more time limited access tokens having a setof access permissions associated with the user account of the user toretrieve, store, modify, update, and/or otherwise access informationwithin a specific time period in the social networking system 101utilizing the application.

Each user account may be further associated with a user profilerepresentative of a user's presence within the social networking system101. Each user profile associated with each user may be represented byuser profile information, which may include, but is not limited to, useridentifier information (e.g., a unique identifier that identifies theuser and the user profile information), user biographic and/ordemographic information, (e.g., user name information which may include,but is not limited to, a first, middle, and/or last name of the user, anentity name associated with the user, contact information of the user,birth date of the user), user profile media information (e.g., profileimage(s) of the user, a focused user profile image of the user, etc.),user location information (e.g., the hometown location of the user, thecurrent location of the user, the work location(s) of the user, etc.),user time zone information (e.g., time zone of the user, etc.), usersocial connections information (e.g., a list of friends, family members,coworkers, teammates, classmates, business associates, of the user),user groups membership information, user forums membership information,user interest information (e.g., the interests listed by the user,movies listed by the user, music listed by the user, books listed by theuser, approvals or “likes” of the user, or any other information thatmay identify the user's interest), user employment history information(e.g., list of current and/or past employers of the user), user socialmessage information (e.g., one or more social networking messages wherethe user is a recipient), user event information (e.g., one or moresocial events associated with the user, etc.), user profile discussioninformation (e.g., one or more profile activities, such as, profileposts in the user profile), user group search information (e.g., one ormore group search queries inputted by the user) and/or any otherpreference/personal information associated with the user.

In some embodiments, the social networking system 101 may enable one ormore applications (e.g., social application 124-1-9 further discussedwith respect to FIG. 1B, etc.) of device 102-a to retrieve at least aportion of the user profile information associated with the user anddisplay at least a portion of the user profile information on one ormore display screens operatively coupled to the devices 102-a. Tofacilitate user interaction between and among users in the socialnetworking system 101, the social networking system 101 may also enableusers to search user profile of other users based at least partially ona received search query and at least a portion of the user profileinformation associated with other users, retrieve at least a portion ofthe user profile information of the other users, and form one or moresocial connections with other users by enabling users via the one ormore applications of devices 102-a to identify other users as the user'sfriend, family member (e.g., spouse, cousin, mother, father,grandmother, grandfather, brother, sisters, daughter, son, etc.),coworker, teammate, classmate, business associate, or any other socialrelationship.

It may be appreciated that the social connections formed between a pairof users may be unidirectional, when only one user in the pair of usersidentifies and acknowledges the type and existence of socialrelationship. Alternatively, the social connections formed between thepair of users may be bidirectional when both users in the pair of usersidentify the same type of social relationship and the existence ofsocial relationship. As such, the social networking system 101 furtherreceive, provide, and/or update user social connections informationwhich may include, but is not limited to, a list of social connectioninformation representative of the social connections of the user (e.g.,the user identifier information or other resource or social networkingobject the user is connected to) and the social connection typeinformation representative of a social connection type (e.g., friend,family member, coworker, teammate, classmate, business associate, and/orany other social relationship) associated with each social connection.Based on the user social connections information of a plurality users,the social networking system 101 may be further configured to determinesocial proximity information which may include, but is not limited to,the degree of separation between one or more pairs of users.

In some embodiments, the social networking system 101 may further enableusers to create, publish, or post one or more profile activities (e.g.,posts, polls, Universal Resource Identifier/Universal Resource Locator(URI/URL) references, etc.), or any other information on the user's ownuser profile represented by the user profile information. Additionally,in some embodiments, the social networking system 101 may further enablesome users to create, publish, post one or more profile activities onuser profiles of other users based at least partially on the user socialconnection information of the other users. The social networking system101 may also enable users to send and/or receive private social messagesto one or more users by communicating the social message informationcomprising one or more private social messages to and from one or moreusers.

To provide collaboration and between and among a specific set of users,including between and among users that may not have a social connectionwith other users in the specific set of users, the social networkingsystem 101 may further enable the association and/or management of oneor more groups and/or one or more forums. In some embodiments, eachgroup may be represented by social group information, which may include,but is not limited to, group identifier information (e.g., a uniqueidentifier that identifies a particular group in the social networkingsystem 101), group privacy information (e.g., group privacy type for theparticular group which may include, but is not limited to, secret grouptype, open group type, or closed group type), group cover imageinformation, group description information (e.g., a descriptionassociated with the particular group), group name information (e.g., thegroup name of the particular group), group owner information (e.g., theowner of the particular group), group location information (e.g., thelocation of the particular group), group membership information (e.g., alist of group members in the particular group), group membership countinformation (e.g., a total number of group members in the particulargroup), or any other information associated with one or more groups.

In some embodiments, the social networking system 101 may enable usersto create one or more groups in the social networking system 101utilizing the one or more applications 124-a-1. Moreover, the socialnetworking system 101 may enable users to create one or more groups byreceiving at least a portion of the social group information (e.g.,group privacy information, group cover image information, groupdescription information, group name information, group ownerinformation, group membership information), and creating a group basedat least partially on the received social group information.

In some embodiments, the social networking system 101 may also enableusers to search for one or more groups and/or one or more forums in thesocial networking system 101 utilizing the one or more applications124-a-1. Moreover, the social networking system 101 may enable users toinput one or more search queries utilizing the one or more applications124-a-1 and providing one or more search results to the one or moreapplications 124-a-1 based at least partially on the one or morereceived search queries. In other embodiments, the search of one or moregroups and/or forums may be limited.

To provide users with these and other social networking services, thesocial networking system 101 may comprise server device 106-1 which mayinclude, among other applications, social networking application 108.The social networking system 101 may further comprise one or moredatastores 112-d operatively coupled to the server device 106. The oneor more datastores 112-d may be configured to store one or moreresources or social networking objects representative of the informationreceived and provided by the social networking system 101. Moreover, thesocial networking objects of the social networking system 101 mayinclude, but is not limited to, one or more groups which may be storedin the groups datastore 112-1, one or more user profiles which may bestored in the user profiles datastore 112-2, one or more comments whichmay be stored in the comments datastore 112-3, one or more activities(e.g., posts, polls, threads, etc.) which may be stored in theactivities datastore 112-4, one or more events which may be stored inevents datastore 112-5 (e.g., social events organized between and amongone or more users, etc.), or any other social networking object that maybe received, stored, provided, or otherwise tracked and/or accessed bythe social networking system 101 to provide the users with these andother social networking services.

The one or more datastores 112-d may further store object connectionsbetween two or more objects or resources in the object connectionsdatastore 112-6. Moreover, the object connections may be representativeof the relationship or links between the two or more objects. The one ormore social networking objects in conjunction with one or more objectsconnections may form a social graph comprising two or more nodesinterconnected via one or more edges, where each node may berepresentative of a social networking object and each edge may berepresentative of the object connections between two or more socialnetworking objects in the social networking system 101. To enable theapplications 124-a-1 to retrieve, modify, update or otherwise access thevarious information managed by the social networking system 101 andrepresented as the social graph, the social networking application 108may further provide a graph application program interface (API)utilizing various protocols (e.g., HTTP, HTTPs, etc.).

In some embodiments, the social networking application 108 may includeone or more social networking components (not shown). At least some ofthe one or more social networking components 110-c may be arranged toimplement at least a portion of the graph API. The one or more socialnetworking components may be generally arranged to enable associationand management of one or more groups by one or more users, enableassociation and management of one or more user profiles and/or useraccounts by one or more users, enable association and management of oneor more forums by one or more users, generate one or more notificationsbased at least partially on one or more users' activity in the socialnetworking system 101, provide the one or more notifications to one ormore applications of devices 102-a to notify one or more users, searchfor information in the social networking system 101 in response to oneor more search queries received from one or more user, and providesearch results to one or more users via the one or more applications124-a-1. The social networking application 108 may further be generallyarranged to communicate with the one or more applications of 102-a viacommunications network 103.

To provide users with power analytics services, the power analyticssystem 105 may include server device 106-2 which may include, amongother applications, power analytics application 109. The power analyticssystem 105 may further include one or more datastores 113-e operativelycoupled to the server device 106-2. The one or more datastores 113-e maybe configured to store information associated with the power analyticssystem 105.

In some embodiments, the one or more datastores 113-e may include, butis not limited to, a device profile datastore 113-1, to store deviceprofile information associated with the power analytics system 105 forat least one device of the one or more devices 102-a. The device profileinformation for at least one device may include, but is not limited to,device application information (e.g., information regarding theapplications that are executed on the devices and each application'scomponent utilizations of the device, etc.), device componentinformation (e.g., the total utilization for each component of thedevice by all applications, etc.), device event information (e.g.,events generated by the devices 102-a, events inputted by the user, suchas, events in a calendar application of the device, device locationinformation (e.g., the physical locations associated with the device,etc.), or any other information for providing power analytics services.Additionally, to enable aggregate context sensitive recommendations, thedevice profile datastore 113-1 may also store at least a portion of theuser profile information (e.g., user identifier information, userlocation information, user social connections information, user eventinformation, etc.) of social networking system 101.

In some embodiments, the one or more datastores 113-e may furtherinclude, but is not limited to, a device analytics datastore 113-2 forat least one device of the one or more devices 102-a. The deviceanalytics datastore 113-2 may be configured to store device analyticsinformation associated with the power analytics system 105 for at leastone device of the one or more devices 102-a. The analytics informationfor at least one device may include, but is not limited to, analyticsmodel information (e.g., one or more generated or determined models fora device for a set time period that predicts or forecasts powerutilization of the device during the set time period, etc.), theanalytics context information (e.g., typical events, meetings,appointments, locations, or any other activity during the set timeperiod, etc.), the analytics power curve information (e.g., informationto construct an analytics power curve such as a power reserve versustime curve representative of typical power utilization of the devicewithin the set time period, etc.), or any other information that mayassist the user of the one or more devices 102-a and/or modify the oneor more devices 102-a to improve power utilization.

The power analytics application 109 may include, but is not limited to,one or more components 114-f. The one or more components may include,but is not limited to, power analytics management component 114-1generally arranged to manage the analysis of device profile informationand/or user profile information received from one or more devices 102-aand provide the analytics information, prediction information, and/orrecommendation to the one or more devices 102-a. The one or morecomponents may further include, but is not limited to, power analyticsmodeling component 114-2 generally arranged to generate analyticsinformation based at least partially on the receive device profileinformation for one or more devices 102-a and/or at least a portion ofuser profile information. The one or more components may also include,but is not limited to, power analytics prediction component 114-3generally arranged generate predicted information and/or recommendationinformation based at least partially on the generated analyticsinformation.

FIG. 1B illustrates an exemplary embodiment of a device 102-1, which maybe a mobile device 102-1 (e.g., a mobile phone or any other a portablecomputing and/or communications device), comprising one or moreapplications 124-1-b, in the mobile predictive power management system100. The mobile device 102-1 may be generally arranged to provide mobilecomputing and/or mobile communications and may include, but is notlimited to, system memory 120, processing component 126, storagecomponent 150, image capture component 154, communications component158, acoustic input/output component 162, touch sensitive displaycomponent 182, haptic component 172, location component 172,acceleration component 180 and power source component 184, where each ofthe components and system memory 120 may be operatively connected viainterconnect 130.

In some embodiments, the processor component 126 may be generallyarranged to execute instruction information including one or moreinstructions. In some embodiments, the processor component 126 may be amobile processor component or system-on-chip (SoC) processor componentwhich may comprise, among other elements, processor circuit 128. Theprocessor circuit 128 may include, but is not limited to, a centralprocessor unit (CPU) comprising a first set of electronic circuitsarranged to execute one or more instructions and/or a graphicsprocessing unit (GPU) comprising a second set of electronic circuitsarranged to execute one or more graphics-oriented instructions.Exemplary processor components 126 may include, but is not limited to,Qualcomm® Snapdragon®, Nvidia® Tegra®, Intel® Atom®, Samsung® Exynos,Apple® A7®, Apple® A8®, or any other type of mobile processing component126 arranged to execute the instruction information including the one ormore instructions stored in system memory 120 and/or storage component150.

In some embodiments, the storage component 150 may be generally arrangedto store information in volatile and/or nonvolatile memory, which mayinclude, but is not limited to, read-only memory (ROM), random-accessmemory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM (DDRAM),synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM),erasable programmable ROM (EPROM), electrically erasable programmableROM (EEPROM) flash memory, polymer memory such as ferroelectric polymermemory, ovonic memory, phase change or ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, solid state memorydevices (e.g., USB memory, solid state drives SSD, etc.), and/or anyother type of storage media configured for storing information.

In some embodiments, the image capture component 154 may be generallyarranged to capture one or more images or a sequence of one or moreimages (e.g., video, etc.) and provide image information and/or videoinformation. The image capture component 154 may include, among otherelements, image sensor 156. Exemplary image sensors 156 may include, butis not limited to, charged-coupled devices (CCD), active-pixel sensors(APS), or any other type of image sensors arranged for convertingoptical images into electronic signals that may be compressed, encoded,and/or stored as image information and/or video information.

In some embodiments, the communications component 158 may be generallyarranged to enable the mobile device 102-1 to communicate with thesocial networking system 101 via the communication network 103. Thecommunications component 158 may include, among other elements, a radiofrequency circuit 160 configured for encoding and/or decodinginformation and receiving and/or transmitting the encoded information asradio signals in frequencies consistent with the one or more wirelesscommunications standards (e.g., Wireless IEEE 802.11, WiMAX IEEE 802.16,Global Systems for Mobile Communications (GSM), Enhanced Data Rates forGSM Evolution (EDGE), Long Term Evolution (LTE), etc.).

In some embodiments, the acoustic input/output (I/O) component 162 maybe generally arranged for converting sound, vibrations, or any othermechanical waves received into electronic signals representative ofacoustic input information utilizing an acoustic sensor 164 (e.g., amicrophone, etc.). Additionally, the acoustic I/O component 162 may befurther arranged to convert electronic signals representative ofacoustic output information utilizing an electroacoustic transducer 166(e.g., a speaker, etc.) to output sound, vibrations, or any othermechanical waves.

In some embodiments, the touch sensitive display component 182 may begenerally arranged to receive and present visual display information,and provide touch input information based on detected touch based orcontact based input. Moreover, the touch sensitive display component 182may include, among other elements, a display device 168 (e.g.,liquid-crystal display, light-emitting diode display, organiclight-emitting diode display, etc.) for presenting the visual displayinformation and touch sensor 170 (e.g., resistive touch sensor,capacitive touch sensor, etc.) associated with the display device 168 todetect and/or receive touch or contact based input information viaassociated with the display device 168. Additionally, in someembodiments, the touch sensor 170 may be integrated with the surface ofthe display device 168, so that a user's touch or contact input maysubstantially correspond to the presented visual display information onthe display device 168.

In some embodiments, the haptic component 172 may be generally arrangedto provide tactile feedback through the housing, case, or enclosure ofthe mobile device 102-1. Moreover, the haptic component 172 may include,among other elements, a vibration circuit 174 (e.g., an oscillatingmotor, vibrating motor, etc.) arranged to convert haptic information tomechanical vibrations representative of tactile feedback.

In some embodiments, the location component 176 may be generallyarranged to receive positioning signals representative of positioninginformation and provide location information (e.g., approximate physicallocation of the current mobile device 102-1) based at least partially onthe received positioning information. Moreover, the location component176 may include, among other elements, a positioning circuit 178 (e.g.,a global positioning system (GPS) receiver, etc.) arranged to determinethe physical location of the mobile device 102-1. In some embodiments,the location component 176 may be further arranged to communicate and/orinterface with the communications component 158 and communicate with thecommunications network 103 in order to provide greater accuracy and/orfaster location acquisition of the location information.

In some embodiments, the acceleration component 180 may be generallyarranged to detect acceleration of the mobile device 102-1 in one ormore axes. The acceleration component 180 may include, among otherelements, motion sensor 182 (e.g., accelerometer, etc.) to convertphysical motions applied the mobile device 102-1 into motioninformation.

In some embodiments, the power source component 184 may be generallyarranged to provide electrical power to the system memory 120 and/or oneor more components of the mobile device 102-1. The power sourcecomponent 184 may include, among other elements, battery 188 (e.g., agroup of cells for storing and providing electrical energy, etc.) andmanagement circuit 186 for providing power source information (e.g.,current charge rate and/or discharge rate of the battery 188, the designcapacity of the battery 188, the current capacity of the battery 188,remaining capacity of the battery 188, etc.).

In some embodiments, the system memory 120 may be generally arranged tostore information in volatile and/or nonvolatile high speed memorysimilar to those discussed with respect to storage component 150. Insome embodiments, at least a portion of the stored information in thesystem memory 120 may comprise instruction information arranged forexecution by the processing component 126. In those embodiments, theinstruction information may be representative of at least one operatingsystem 122-1, one or more applications 124-1-b, and/or any otherprograms and/or modules. In some embodiments, the one or moreapplications 124-1-b may include, but is not limited to, a managementapplication 124-1-2 generally arranged to manage the execution of theone or more applications 124-1-b of the mobile device 102-1. The one ormore applications 124-1-b may further include, but is not limited to,power application 124-1-1. The one or more applications 124-1-b may alsoinclude, but is not limited to, non-power applications, which mayinclude, but is not limited to, management application 124-1-2, imagingapplication 124-1-3, messaging application 124-1-4, phone application124-1-5, e-mail application 124-1-6, entertainment application 124-1-7,browser application 124-1-8, social application 124-1-9, locationapplication 124-1-10, calendar application 124-1-11, audio/videoapplication 124-1-12, or any other application that is not the powerapplication 124-a-1.

In some embodiments, the operating system 122-1 may comprise a mobileoperations system 122-1 (e.g., Apple®, i0S®, Google® Android®, HP®WebOS®, Microsoft® Windows Phone®, Microsoft® Windows®, etc.) generalarranged to manage hardware resources (e.g., one or more components ofthe mobile device 102-1) and/or software resources (e.g., one or moreapplications 124-1-b of the mobile device 102-1). The operating system122-1 may be further arranged to modify execution states associated withone or more applications 124-1-b based at least partially on informationreceived from one or more components (e.g., touch sensitive displaycomponent 182, power source component 184, location component, audio I/Ocomponent 158, etc.) and/or one or more applications (e.g., managementapplication 124-1-1, phone application 124-1-5, e-mail application124-1-6, messaging application 124-1-4, social application 124-1-9,etc.).

In some embodiments, the operating system 122-1 may be arranged tomodify execution states by transitioning the one or more applications124-1-b between and among the one or more execution states. The one ormore execution states may include, but is not limited to, foregroundstate, non-execution state, suspended state, and/or background state. Insome embodiments, applications 124-1-b may be initially in thenon-execution state where the instruction information associated withapplications 124-1-b in the non-execution state are not executed by theprocessor component 126 nor scheduled for execution by the processorcomponent 126.

In some embodiments, the operating system 122-1 may transition anapplication (e.g., power application 124-1-1) initially in thenon-execution state to the foreground state, in response to receiving arequest to execute or initiate the execution of the applicationpreviously in the non-execution state (e.g., launching the application).In some embodiments, the operating system 122-1 may transition theapplication in a non-execution state to the foreground state where theinstruction information associated with the application is executed orscheduled for execution by the processor component 126 as one or moreprocesses in order to provide mobile computing operations associatedwith the application to the one or more users. In some embodiments, theoperating system 122-1 may be further arranged to retrieve at least aportion of the application that is to be executed from the storagecomponent 150 and store at least a portion of instruction informationassociated with an application (e.g., management application 124-1-2,power application 124-1-1, imaging application 124-1-3, etc.) in systemmemory 120 so that processing component 126 may retrieve and execute theinstruction information associated with the application from systemmemory 120 as one or more processes. It may be appreciated that when anapplication (e.g., power application 124-1-1) is in the foregroundstate, one or more UI views associated with the application in theforeground state may be at least partially visible on the display device168 of the touch sensitive display component 182 in order to processinformation (e.g., input information, etc.) received from one or morecomponents (e.g., touch sensor 170, etc.) of the mobile device 102-1 viaone or more asynchronous and/or synchronous events.

In some embodiments, the operating system 122-1 may transition anapplication (e.g., power application 124-1-1) from the foreground stateto the suspended state, in response to a request to launch a differentapplication (e.g., transitioning the different application, such as, forexample, browser application 124-1-8 from non-execution state to theforeground state), switch to a different application (e.g.,transitioning the different application, such as, for example, browserapplication 124-1-8 from background state to the foreground state), orresume a different application (e.g., transitioning the differentapplication, such as, for example, browser application 124-1-8 fromsuspended state to the foreground state).

In some embodiments, the operating system 122-1 may transition theapplication from the foreground state to the suspended state where theinstruction information associated with the application may betemporarily stopped or prevented from further execution by the processorcomponent 126 and the execution context information (e.g., theinformation stored in processor registers, at least a portion of theapplication allocated in system memory 120, etc.) may be saved to thesystem memory 120 and/or storage component 150. In some embodiments, theoperating system 122-1 may continue to store at least a portion of thesuspended application in system memory 120 so that the suspendedapplication may continue to reside or remain in system memory 120 whichmay enable the application in the suspended state to be quickly resumed(e.g., transitioning the application from the suspended state to theforeground state).

In some embodiments, the operating system 122-1 may transition anapplication (e.g., power application 124-1-1) may transition from theforeground state to the suspended state, in response to a request tolaunch a different application (e.g., transitioning the differentapplication, such as, for example, browser application 124-1-8 fromnon-execution state to the foreground state), switch to a differentapplication (e.g., transitioning the different application, such as, forexample, browser application 124-1-8 from background state to theforeground state), or resume a different application (e.g.,transitioning the different application, such as, for example, browserapplication 124-1-8 from suspended state to the foreground state). Insome embodiments, the operating system 122-1 may transition theapplication from the foreground state to the background state where alimited portion of the instruction information (e.g., instructioninformation associated with a background thread of the application,etc.) associated with the application is continued for further executionby the processor component 126 while the one or more UI views may not bevisible or partially visible on the display device 168.

In some embodiments, the operating system 122-1 may transition anapplication (e.g., power application 124-1-1) from the foreground stateto non-execution state, in response to a request to close, terminate,and/or kill the application or the complete execution of the instructioninformation associated with the application by the processing component126. In some embodiments, the operating system 122-1 may transition theapplication in the foreground state to the non-execution state where theprocessing component 126 stops executing most if not all instructioninformation associated with the application. In some embodiments, theoperating system 122-1 may also free (e.g., remove, purge, otherwisemake available, etc.) at least a portion of the system memory 120previously storing the instruction information and/or execution contextinformation associated with the application transitioning to thenon-execution state.

In some embodiments, the management application 124-1-2 may be visuallypresented as a home screen UI view (not shown) comprising a plurality ofUI elements representative of applications 124-1-b and may be generallyarranged to launch on startup of the mobile device 102-1 and operatingsystem 122-1. Additionally, the management application 124-1-2 may bearranged to receive touch input information from the touch sensitivedisplay component 182 in order to launch one or more applications124-1-b. In some embodiments, the management application 124-1-2 may bearranged to request the operating system 122-1 to launch or initiate theexecution of one or more applications 124-1-b of mobile device 102-1based at least partially on the received input information (e.g., touchbased input information received from touch sensor 170, etc.). In someembodiments, the imaging application 124-1-3 may be generally arrangedto receive, store, display and/or otherwise manage image informationand/or video information via the image capture component 154. In someembodiments, the message application 124-1-4 may be generally arrangedto receive, transmit, display, and/or otherwise manage one or moremessages including multimedia messages (e.g., pictures, videos, audio,etc.) utilizing one or more cellular and/or internet messaging servicesvia one or more components of the mobile device 102-1. In someembodiments, the phone application 124-1-5 may be generally arranged toreceive, make, display, and/or otherwise manage one or more audio and/orvideo phone calls utilizing one or more cellular and/or internet phoneservices via one or more components of the mobile device 102-1. In someembodiments, the e-mail application 124-1-6 may be generally arranged toreceive, compose, display, and/or otherwise manage one or more one ormore e-mails messages utilizing one or more components of the mobiledevice 102-1. In some embodiments, the entertainment application 124-1-7may be generally arranged to provide mobile entertainment such as, forexample, a mobile video game utilizing the CPU and/or the GPU of theprocessing component 126. In some embodiments, the browser application124-1-8 may be generally arranged to access one or more web pagesutilizing one or more utilizing one or more components of the mobiledevice 102-1. In some embodiments, the social application 124-1-9 may begenerally arranged to provide social networking services between andamong one or more users of one or more devices (e.g., Twitter®, Vine®,Facebook®, Reddit®, Digg®, Imgur®, etc.). In some embodiments, thelocation application 124-1-10 may be generally arranged to providelocation and/or direction services and visually present the currentlocation and/or directions to a location on a global and/or regionalmap. In some embodiments, the calendar application 124-1-11 may begenerally arranged to store one or more appointments, meetings, and/orreminders, for a user of the mobile device 102-1. In some embodiments,the audio/video application 124-1-12 may be generally arranged torecord, playback, or output audio and/or video information received viacommunications component 158 and/or stored in memory 120 and/or storagecomponent 150.

In some embodiments, the power application 124-1-1 may be generallyarranged to enable one or more users of the mobile device 102-1 tomanage consumption of the mobile 102-1. In some embodiments, the powerapplication 124-1-1 may be generally launched from the home screen UIview (not shown) of the management application 124-1-2 based at leastpartially on touched input information received from the touch sensitivedisplay component 182. In some embodiments, the power application124-1-1 may be configured to request access and/or obtain access to userprofile information from social networking system 101.

Additionally or alternatively, in some embodiments, the powerapplication 124-1-1 may be configured to enable mobile deep linkingutilizing a deep link reference (e.g., a universal resource identifier(URI), universal resource locator (URL), etc.) associated with the powerapplication 124-1-1. The deep link reference associated with the powerapplication 124-1-1 may include, but is not limited to, applicationidentification information (e.g., a unique identifier associated withthe power application 124-1-1). In some embodiments, the deep linkreference associated with the power application 124-1-1 may furtheroptionally include, but is not limited to, application locationinformation (e.g., an identifier associated with a specific locationwithin power application 124-1-1, such as, group identifier information)configured to enable a non-power application (e.g., home screen UI viewof the management application 124-1-2, imaging application 124-1-3,messaging application 124-1-3, phone application 124-1-5,e-mail-application 124-1-6, entertainment application 124-1-7, browserapplication 124-1-8, social application 124-1-9, or any otherapplication 124-1-b that is not power application 124-a-1) to directlylaunch or transition to a specific location (e.g., one or more viewsidentified by application location information) within the powerapplication 124-1-1 from the non-power application based at leastpartially on touch input information received from the touch sensitivedisplay component 182.

FIG. 1C illustrates an exemplary embodiment of the mobile powerapplication 124-1-1 for managing power utilization of one or more mobiledevices 102-a (e.g., mobile device 102-1). The power application 124-1-1may include one or more power components 190-e. The one or more powercomponents 190-e may include, but is not limited to, power managementcomponent 190-1, power rendering component 190-2, power monitoringcomponent 190-3, power input component 190-4, and power communicationscomponent 190-5. Optionally, the one or more power components 190-e mayfurther include, but is not limited to, power authentication component190-6 and/or power settings component 190-7.

The power authentication component 190-6 may be generally arranged toauthenticate a user having an associated user account in the socialnetworking system 101 based on at least a portion of the user accountinformation (e.g., user account identifier and user accountauthentication token) inputted by the user utilizing, for example, anon-screen virtual keyboard or any other input information. Once the userhaving the associated user account has been authenticated, the powerauthentication component 190-6 may be configured to receive one or moretime limited access tokens from the social networking application 108,and store the one or more time limited access tokens in the storagecomponent 150 and/or system memory 120 of the mobile device 102-1 foruse by the one or more power components 190-e to access information inthe social networking system 101 via the power communications component190-5.

The power communications component 190-5 may be generally arranged toreceive, transmit, and/or otherwise facilitate communications ofinformation 192 between the one or more power components 190-e and thepower analytics system 105 utilizing one or more APIs, one or morecomponents of the mobile device 102-1 (e.g., the communicationscomponent 158), and/or communications network 103. Optionally, powercommunications component 190-5 may also be generally arranged toreceive, transmit, and/or otherwise facilitate communications betweenthe one or more power components 190-e and the social networkingapplication 108 utilizing one or more APIs (e.g., graph API), thereceived, stored, and/or cached one or more time limited access tokens,one or more components of the mobile device 102-1 (e.g., thecommunications component 158), and communications network 103.

The power monitoring component 190-3 may be generally arranged to managecapturing device profile information and/or storing the captured deviceprofile information. In some embodiments, the power monitoring component190-3 may be configured to capture device application information (e.g.,device application information 210-1 further discussed with respect toFIG. 2) by interfacing with one or more APIs of the operating system122-1 (e.g., calling one or more API functions of the operating system122-1, etc.) to retrieve and/or store a list of applications informationfor each application. The application information may include, but isnot limited to, application identification information (e.g.,application name, application identifier, etc.), application executioninformation (e.g., application execution state, application componentutilization such as CPU utilization and/or GPU utilization of theprocessing component 126 of mobile device 102-1 by the application),and/or any other information associated with one or more applications124-1-b of mobile device 102-1.

In some embodiments, the power monitoring component 190-3 may also beconfigured to capture device component information (e.g., devicecomponent information 210-2 further discussed with respect to FIG. 2) byinterfacing with one or more APIs of the operating system 122-1 (e.g.,calling one or more API functions implemented or exposed by theoperating system 122-1, etc.) and/or APIs of the one or more components(e.g., calling one or more API functions implemented or exposed bydevice drivers for one or more components) to retrieve and/or store alist of component information for one or more components of the mobiledevice 102-1. The component information for one or more components mayinclude, but is not limited to, component identification information(e.g., component name, component identifier, etc.), component designinformation (e.g., design capacity for the power source component 184,design operating frequency or frequencies for the CPU and/or GPU of theprocessing component 126, etc.), component status information (e.g.,current discharge rate for the power source component 184, currentcharge capacity for the power source component 184, current total CPUand/or GPU utilization of the processing component 126, etc.), currentpower state information (e.g., non-functional/disabled state, low powerstate, active state, high performance state, etc.), or any otherinformation associated with one or more components of the mobile device102-1.

In some embodiments, the power monitoring component 190-3 may also beconfigured to capture device event information (e.g., device eventinformation 210-3 further discussed with respect to FIG. 2)representative of one or more device events associated with the mobiledevice 102-1 and/or the user of the mobile device 102-1 by interfacingwith one or more APIs of the operating system 122-1, one or more APIs ofthe one or more components, and/or interfacing one or more APIs of thecalendar application 124-1-11. Moreover, the device event informationmay further include, but is not limited to, one or more power eventsrepresented by device power event information (e.g., battery chargeevent, battery discharge event, etc.), one or more application eventsrepresented by device application event information (e.g., applicationinstall event, application uninstall event, application update event,etc.), and/or one or more calendar events represented by device calendarevent information (e.g., appointments, meetings, reminders for the userof the mobile device 102-1).

In some embodiments, the power monitoring component 190-3 may also beconfigured to capture device location information by interfacing withone or more APIs of the operating system 122-1 and/or interfacing withone or more APIs of the location component. Moreover, the devicelocation information may include, but is not limited to, devicecoordinates information (e.g., approximate GPS coordinates associatedwith the location of the mobile device 102-1, etc.).

It may be appreciated that because power monitoring component 190-3 maycapture and/or store vast amounts of device profile information whichmay contain private information regarding the user, the users mayutilize one or more UI views and/or UI elements visually presented bythe power settings component 190-7 on a display screen (not shown) ofthe mobile device 102-1 to modify or update the privacy limitationinformation in order to preserve their privacy and limit the amount andtype of information captured, stored, and/or otherwise transmitted bythe power monitoring component 190-3.

In some embodiments, the device profile information may be captured,stored, and/or transmitted to the power analytics application 109 of thepower analytics system 105 on a periodic basis (e.g., every 30 seconds,1 minute, 5 minutes, 10 minutes, 15 minutes, etc.) based at leastpartially on mobile power application preferences information. Forexample, the device profile information may be captured, stored, and/ortransmitted every 5 minutes while the power application 124-1-1 isexecuting in either in the foreground and/or background state, when themonitoring frequency information and/or transmission frequencyinformation of the mobile power application preferences informationindicate that the device profile information is to be captured, stored,and/or transmitted every 5 minutes.

The mobile power application preferences information may include, but isnot limited to, monitoring frequency information (e.g., the frequency ofcapturing and/or storing device profile information by the application124-1-1, etc.), transmission frequency information (e.g., the frequencyof transmitting the captured and/or stored device profile information tothe power analytics system 105, etc.), receipt frequency information(e.g., the frequency of requesting and receiving analytics information,predicted information, and recommendation information for theapplication 124-1-1, etc.), power reserve threshold limit information(e.g., the amount of power to be reserved on the mobile device, etc.),and/or privacy limitation information (e.g., privacy limitations onspecific information to be captured, stored, and/or transmitted by theapplication 124-1-1, etc.)

The power rendering component 190-2 may be generally arranged to providevisual display information comprising to the touch sensitive displaycomponent 182 to render one or more UI views comprising one or more UIelements for visual presentation on the display device 168. In someembodiments, the power rendering component 190-2 may be further arrangedto provide visual display information to the touch sensitive displaycomponent 182 to render one or more animated transitions between the oneor more views and/or one or more animated UI elements for visualpresentation on the display device 168.

The power input component 190-4 may be generally arranged to provideuser input information which may include, but is not limited to, one ormore gestures and provide character input information utilizing one ormore components of the mobile device 102-1 (e.g., touch sensitivedisplay component 182). In some embodiments, the power input component190-4 may be configured to receive touch input information from thetouch sensitive display component 182 and determine one or more fingergestures based at least partially on the received touch inputinformation. In some embodiments, the power input component 190-4 may beconfigured to provide user input information including the characterinput information to the based on one or more characters inputted by auser utilizing an on-screen virtual keyboard visually presented on atleast a portion of the display device 168. Moreover, the character inputinformation may be determined based at least partially on one or morecontacts detected in a predefined region associated with the on-screenvirtual keyboard.

In some embodiments, the power input component 190-4 may be furtherconfigured to detect a selection finger gesture to select a selectableUI element based at least partially on the received touch inputinformation, the received touched input information may include, but isnot limited to, finger contact at a first location in a predefinedregion associated with the UI element visually presented on the displaydevice 168 for a predefined time period (e.g., less than one second),and termination of the finger contact at the first location of thepredefined region.

In some embodiments, the power input component 190-4 may be alsoconfigured to detect a scroll finger gesture to scroll a scrollable UIelement and/or scrollable UI view based at least partially on thereceived touch input information, the received touched input informationmay include, but is not limited to, finger contact at a first locationin a predefined region associated with the scrollable UI element and/orscrollable UI view visually presented on the display device 168,initiating movement of the finger contact within a predefined timeperiod after the finger contact (e.g., less than one second), continuousmovement of the finger contact from the first location to a secondlocation in at least one direction (e.g., up direction, down direction,left direction, right direction, or any combination thereof), andtermination of the finger contact at the second location.

It may be appreciated that in some embodiments, UI elements and/or UIviews may be configured as selectable and/or scrollable, and the powerinput component 190-4 may be configured to determine the respectivefinger gesture based at least partially on the received touch inputinformation.

The power settings component 190-7 may be generally arranged to managethe settings associated with the power application 124-1-1 utilizing oneor more components of the mobile device 102-1 (e.g., touch sensitivedisplay component 182, storage component 150, etc.). In someembodiments, the power settings component 190-7 may be configured tomodify and/or update user mobile power application preferencesinformation stored or cached in storage component 150 and/or systemmemory 120, based at least partially on user input information providedby the power input component 190-4.

In some embodiments, the power settings component 190-7 may beconfigured to modify, update, and/or otherwise synchronize the usermobile power application preferences information stored or cached instorage component 150 and/or system memory 120 with the user mobilepower application preferences information stored in the power analyticssystem 105 and associated with device identifier information for aparticular mobile device, so that any instance of the power applications124-a-1 for a user may share and/or utilize the latest user mobile powerapplication preferences information regardless of which mobile devicethe user is currently using. Additionally, the mobile power applicationpreferences information may also be utilized by power analyticsapplication 109 of the power analytics system 105 to generateand/provide analytics information, predicted information, and/orrecommendation information to the mobile device of the user.

The power management component 190-1 be generally arranged to providepower management of the mobile device 102-1. To provide powermanagement, the power management component 190-1 may be generallyarranged to request or initiate monitoring device profile information ofthe mobile device 102-1, provide the device profile information to poweranalytics application 109, receive analytics power curve information,analytics context information, predicted power curve information,predicted context information, and context sensitive recommendationinformation, store or cache the received information in system memory120 and/or storage component 150, provide the stored or cachedinformation to the power rendering component 190-2 for visualpresentation in one or more UI views.

In some embodiments, the power management component 190-1 may beconfigured to generate a device identifier information (e.g., ahexadecimal value) based at least partially on one or more components(e.g., media access control (MAC) address, international mobile stateequipment identity (IMEI) of the communications component 158, etc.).The device identifier information may be configured to uniquely identifya mobile device (e.g., mobile device 102-1) and may be associated withthe device profile information of the mobile device (e.g., mobile device102-1) and/or the user profile information for the user of the mobiledevice (e.g., mobile device 102-1). The power management component 190-1may be further configured to initiate the monitoring of device profileinformation of the mobile device 102-1 by the power monitoring component190-3 on a periodic basis (e.g., every 30 seconds, 1 minute, 5 minutes,10 minutes, 15 minutes, etc.) and transmit the collected device profileinformation to the power analytics management component 114-1 on aperiodic basis.

In some embodiments, the power management component 190-1 may be furtherconfigured to receive analytics information (e.g., analytics modelinformation, analytics power curve information, analytics contextinformation), and predicted power curve information, predicted contextinformation, and/or context sensitive recommendation information on aperiodic basis (e.g., every 30 seconds, 1 minute, 5 minutes, 10 minutes,15 minutes, etc.) based at least partially on mobile power applicationpreferences information. Additionally or alternatively, the powermanagement component 190-1 may be further configured to receive theinformation initiated by power analytics application 109 (e.g.,push-based or server initiated, etc.), when the generated predictedpower curve information indicates that the power utilization deviatesfrom the analytics power curve information. Additionally oralternatively, the power management component 190-1 may be furtherconfigured to request and receive the information, in response toreceiving user input to view the information (e.g., predicted powercurve information, predicted context sensitive recommendationinformation, etc.)

In some embodiments, the power management component 190-1 may beconfigured to visually present one or more UI views (not shown) on adisplay screen of the touch sensitive display component 182. The one ormore UI views may include, but is not limited to, one or more UIelements (not shown) configured to visually present analyticsinformation, predicted information, recommendation information, and/orany other information to assist the user of the mobile device 102-1 inmanaging power utilization.

In some embodiments, the power management component 190-1 may optionallyenable a user to log into the social networking system 101 via powerauthentication component 190-6 based at least partially on user accountinformation. After the successful authentication of the user by thepower authentication component 190-6 and receipt of the one or more timelimited access tokens from the social networking application 108, thepower management component 190-1 may initiate one or more requests forat least a portion of the user profile information associated with theuser having the associated user account via the power communicationscomponent 190-5. Moreover, the user profile information may include, butis not limited to, user identifier information, user locationinformation, user social connections information, user eventinformation, and/or any other user profile information. The powermanagement component 190-1 may also, optionally, provide at least aportion of the received user profile information to the power analyticsapplication 109.

FIG. 2 illustrates an exemplary embodiment of determining predictedinformation and/or recommendation information. As illustrated in FIG. 2,the operating environment 200 may include, but is not limited to poweranalytics application 109 of the power analytics system 105. The poweranalytics application 109 may include, but is not limited to, poweranalytics management component 114-1.

In some embodiments, the power analytics management component 114-1 maybe configured to receive device identifier information and deviceprofile information associated with the received device identifierinformation from one or more devices 102-a (e.g., mobile device 102-1)and store the received device identifier information and device profileinformation associated with the received device identifier informationin the device profile datastore 113-1. The device profile informationmay include, but is not limited to, device application information210-1, device component information 210-2, device event information210-3, and/or device location information 210-4.

Optionally, the power analytics management component 114-1 may also beconfigured to receive at least a portion of the user profile information210-5 associated with the user of the mobile device having theassociated device identifier information in the device profile datastore113-1. The power analytics management component 114-1 may be furtherconfigured to store the received user profile information 210-5 and/orassociate device identifier information in the device profile datastore113-1.

In some embodiments, the power analytics management component 114-1 maybe configured to request the generation of analytics information by thepower analytics modeling component 114-2 and predicted information(e.g., predicted power curve information 214-4, predicted contextinformation 212-5, predicted power event information 212-7, etc.) and/orrecommendation information (e.g., context sensitive recommendationinformation 212-6, etc.) by the power analytics prediction component114-3. The analytics information may include, but is not limited to,analytics model information 212-1, analytics power curve information212-2, and/or analytics context information 212-3. The predictioninformation may include, but is not limited to, predicted power curveinformation 212-4 and predicted context information 212-5. Therecommendation information may include, but is not limited to, contextsensitive recommendation information 212-6.

In some embodiments the power analytics management component 114-1 maybe configured to request the generation of analytics information,predicted information, and/or recommendation information on a periodicbasis (e.g., every 5 minutes, every 10 minutes, every 15 minutes, etc.),and/or in response to one or more requests received from one or moredevices 102-a for predicted information based at least partially on theuser mobile power application preferences information associated withthe mobile device (e.g., mobile 102-1). Additionally, in someembodiments, the power analytics management component 114-1 may befurther configured to provide the generated analytics information,predicted information, and/or recommendation information on a periodicbasis (e.g., every 5 minutes, every 10 minutes, every 15 minutes, etc.),and/or in response to the one or more to one or more requests receivedfrom one or more devices 102-a based at least partially on the mobilepower application preferences information. Furthermore, the poweranalytics management component 114-1 may be configured to provide theanalytics information, predicted information, and/or recommendationinformation, in response to determining, based on the current powerutilization for a mobile device (e.g., mobile device 102-1, etc.), thatthe mobile device will likely fall below a power reserve threshold limit(e.g., power reserve threshold limit 344 further discussed with respectto FIG. 3D-3F, etc.) before reaching the time associated with apredicted charge event (e.g., predicted charge events 350-1, 350-2,350-3 further discussed with respect to FIG. 3D-3F, etc.).

The power analytics application 109 may further include, but is notlimited to, a power analytics modeling component 114-2 which may begenerally arranged to analyze past or historic device profileinformation in order to estimate or forecast the power utilization ofone or more mobile devices 102-a for a future set time period orinterval on a reoccurring day of the week (e.g., 24 hour period of timefor every Monday, etc.). Moreover, the power analytics modelingcomponent 114-2 may be configured to receive device profile informationfor one or more mobile devices 102-a (e.g., mobile device 102-1, etc.)and/or optionally, at least a portion of user profile information forusers of the one or more mobile devices 102-a. The power analyticsmodeling component 114-2 may be further configured to generate theanalytics information (e.g., analytics model information 212-1,analytics power curve information 212-2, analytics context information212-3, etc.) based at least partially on the received device profileinformation and/or user profile information utilizing well-known machinelearning (e.g., decision tree learning, artificial neural networks,clustering, Bayesian networks, etc.) techniques, methods, and/oralgorithms.

In some embodiments, the analytics power curve information 212-2 may berepresentative of a typical estimated or forecasted power utilizationfor the mobile device 102-1 during a set time period or interval for arecurring day of the week. In some embodiments, the analytics powercurve information 212-2 may be generated utilizing well-known machinelearning techniques, methods, and/or algorithms based at least partiallyon the aggregate of past power curve information 214-3 for multiplereoccurring days of the week (e.g., the past power curve information forevery Monday, or the past context information for every Tuesday, etc.).

The past power curve information 214-3 may be representative of a powerreserve versus time curve for the power utilization of the mobile device102-1 as monitored, stored, and/or transmitted by the power application124-1-1 before the current time but still within a set time period orinterval for a recurring day of the week, i.e., a calculated usage ofpower utilization for the mobile device 102-1 up to the current time. Byway of example, the past power curve information 214-3 may berepresentative of a power reserve versus time curve starting at time12:00 AM to 8 AM on Monday for mobile device 102-1, when the currenttime is 8 AM on Monday and the power analytics management component114-1 has been receiving device profile information from the mobiledevice 102-1 on a periodic basis since 12:00 AM on Monday. The exampleis not limited in this context.

In some embodiments, the power analytics modeling component 114-2 may beconfigured to generate the past power curve information 214-3 based atleast partially on the device profile information (e.g., deviceapplication information 210-1, device component information 210-2,device events information 210-3, device location information 210-4,etc.) for the mobile device 102-1 received and/or time stamped during aset time period or interval in the past (e.g., set time period from12:00 AM to 11:59 PM) to the current or present time (e.g., 8 AM) forthe reoccurring day of the week (e.g., Monday) for mobile device 102-1.

In some embodiments, the generated analytics power curve information212-2 may include, but is not limited to, one or more power reserveversus time curves for the set time period or interval. In someembodiments, the one or more power reserve versus time curves may alsocontain one or more estimated or approximate charge events during theset time period or interval. Additionally, in some embodiments, thepower reserve, which may be typically associated with ampere-hour (Ah)or milliampere-hour (mAh), may be normalized on a scale between 0 and100 to indicate the percentage of the remaining power reserve withrespect to time, regardless of actual capacity of battery 188.

In some embodiments, the generated analytics model information 212-1 mayinclude, but is not limited to, analytics power utilization informationand/or analytics runtime information. The analytics power utilizationinformation may be representative of one or more power models thatestimate or approximate the power utilization of one or moreapplications 124-1-b, the operating system 122-1, and/or the one or morecomponents of the mobile device 102-1 as one or more linear and/ornon-linear power utilization functions. For example, the one or morelinear and/or nonlinear discrete or continuous functions with one ormore input parameters including, but is not limited to, a time durationparameter (e.g., 15 minutes, 30 minutes etc.) and starting power reserveparameter and output of a linear or nonlinear discrete or continuouspower utilization curve that approximate the power utilization for thattime duration and starting power reserve. The analytics runtimeinformation may be representative of average foreground and/orbackground execution time of the one or more applications 124-1-b,during one or more analytics contexts (e.g., meetings, appointments,reminder, social events, etc.) or in response to one or more deviceapplication events (e.g., installing the one or more application,updating one or more application, etc.).

By way of example, the one or more linear and/or non-linear powerutilization functions may include, but is not limited to, a functionthat estimates or approximates the power utilization of an applicationsuch as the audio/video application 124-1-12 executing in the foregroundstate and visually presenting video information on the touch sensitivedisplay component 182 for a specific period of time on the mobile device102-1. In another example, the one or more linear and/or non-linearpower utilization functions may include, but is not limited to, afunction that estimates or approximates the power utilization of anapplication such as the audio/video application 124-1-12 executing inthe background state and recording audio for a specific period of timeon the mobile device 102-1. The examples are not limited in thiscontext.

In some embodiments, the power analytics modeling component 114-2 may beconfigured to generate analytics context information 212-3 utilizingwell-known machine learning techniques, methods, and/or algorithms basedat least partially on the aggregate of past context information 214-1for multiple reoccurring days of the week (e.g., the past contextinformation for every Monday, or the past context information for everyTuesday, etc.) The past context information 214-1 may be representativeof one or more past contexts (e.g., past contexts 342-1 of FIG. 3D,etc.) that already occurred at an approximate time, approximatelocation, for an approximate duration in the past. By way of example, anexemplary past context may include a meeting that has already occurredbetween 9:30 AM and 10:30 AM at Location D on Monday, when the currentday and time is Monday at 11:00 AM. The example is not limited in thiscontext. In some embodiments, the power analytics modeling component114-2 may be configured to generate the past context information 214-1,based at least partially on device profile information (e.g., deviceevent information 210-3, device location information 210-4, etc.) and/oroptionally, user profile information 210-5 (e.g., user eventinformation, user location information, etc.) for a set time period orinterval of a recurring day of the week. The generated past contextinformation 214-2 may include, but is not limited to, past locationcontext information, past event context information, and/or pastapplication context information.

The past location context information may be representative of one ormore past location contexts that identify one or more past locations ina past set time period or interval of time for a reoccurring day of theweek. Each past location context may be associated with a past locationcontext start time, past location context end time, past locationcontext duration, and/or past location category (e.g., home, work,school, traveling, etc.).

The past event context information may be representative of one or morepast events contexts that identify one or more past device eventsrepresented by device event information 215-3 (e.g., device power eventsrepresented by device power event information, device application eventsrepresented by device application event information, device calendarevents represented by device calendar event information, etc.) and/oroptionally, one or more past social events represented by user eventinformation of the user profile information 210-5. Each past eventcontexts may be associated with a past event context start time, pastevent context end time, past event context duration, past event category(e.g., calendar event, power event, application event, social event,etc.), and/or past event sub-category associated with each past eventcategory (e.g., appointments, meetings, and/or reminders associated withcalendar event category, and/or social event category, battery chargeevent and/or battery discharge event associated with power eventcategory, application install event, application uninstall event, and/orapplication update event associated with application event category,etc.).

The past application context information, may be representative of oneor more past application contexts. The one or more past applicationcontext may correspond to and/or be associated with a past locationcontext and/or past event context represented by the past event contextinformation and/or past location context information, respectively. Eachpast application context may also provide a list of applications thatmay have been executed during, after, and/or substantiallycontemporaneously (e.g., within 5 minutes, 10 minutes, 15 minutes, etc.)with the occurrence of a past location context and/or past eventcontext. For example, a past application context may correspond to or beassociated with a past event context (e.g., an application installevent, etc.) represented by past event context information to storeand/or provide lists of applications that have been executed during,after, and/or substantially contemporaneously (e.g., within 5 minutes,etc.) to the occurrence of that past event context (e.g., theapplication install event, etc.).

In some embodiments, each past application context may also beassociated with past runtime information. The past runtime informationmay be representative of past mobile device 102-1 component utilization(e.g., processing component 126 utilization, etc.) for each applicationthat the mobile device 102-1 has executed during the corresponding pastlocation context information, past event context information, so thatone or more predominant applications (e.g., applications with thehighest processing component 126 utilization, etc.) and/ornon-predominant applications utilized may be identified. The pastruntime information may also include, but is not limited to, applicationexecution duration and their respective execution states (e.g.,foreground state, background state, suspended state, etc.) for eachapplication that was executed in the past during, after, and/orsubstantially contemporaneously (e.g., within 5 minutes, 10 minutes, 15minutes, etc.) with the occurrence of one or more past location contextsand/or past event contexts.

The generated analytics context information 212-3 may be representativeof one or more estimated or forecasted analytics contexts that may or islikely to occur at an approximate or estimated time, an approximate orestimated location, for an approximate or estimated duration in thefuture but has not yet occurred. Each estimated or forecasted analyticscontext may substantially correspond to at least a portion of ananalytics power curve represented by the analytics power curveinformation 212-2. In some embodiments, the generated analytics contextinformation 212-3 may include, but is not limited to, analytics locationcontext information, analytics event context information, and/oranalytics application context information.

The analytics location context information may be representative of oneor more analytics location contexts that identify an estimated orforecasted location for a user in a future set time period on areoccurring day of the week, which may further infer the generalactivity or activities for the user during the set time period orinterval of time on the recurring day of the week. Each analyticslocation context may be associated with an analytics location contextstart time, analytics location context end time, analytics locationcontext duration, and/or analytics location category (e.g., home, work,school, traveling, etc.).

The analytics event context information may be representative of one ormore analytics event contexts that identify one or more estimated orforecasted device events and/or optionally, one or more social events ofthe user during a future set time period or interval on a recurring dayof the week. Each analytics event context may be associated with ananalytics event context start time, analytics event context end time,analytics event context duration, analytics event category (e.g.,calendar event, power event, application event, social event, etc.),analytics event sub-category associated with each past event category(e.g., appointments, meetings, and/or reminders associated with calendarevent category and/or social event category, battery charge event and/orbattery discharge event associated with power event category,application install event, application uninstall event, and/orapplication update event associated with application event category,etc.).

The analytics application context information, may be representative ofone or more analytics application contexts. The one or more analyticsapplication context may correspond to and/or be associated with ananalytics location context represented by the analytics location contextinformation and/or analytics event context analytics event contextinformation. Each analytics application context may also provide anestimated or forecasted list of applications for each analytics locationcontext and/or analytics event context that the mobile device 102-1 isestimated or forecasted to execute during, after, and/or substantiallycontemporaneously (e.g., within 5 minutes, 10 minutes, 15 minutes,etc.), with each analytics location context and/or analytics eventcontext. For example, an analytics application context may correspond toor be associated with a device application event (e.g., applicationinstall event, etc.) to provide an estimated or forecasted list ofapplications that may is estimated or forecasted to be executed during,after, and/or substantially contemporaneously (e.g., within 5 minutes,10 minutes, 15 minutes, etc.) to the occurrence of that deviceapplication event (e.g., application install event, etc.).

In some embodiments, each analytics application context may also provideanalytics runtime information. The analytics runtime information may berepresentative of estimated or forecasted mobile device 102-1 componentutilization (e.g., processing component 126 utilization, etc.) for eachapplication estimated or forecasted for execution by the mobile device102-1, so that one or more predominant applications (e.g., applicationswith the highest processing component 126 utilization, etc.) and/ornon-predominant applications utilized may be identified. The analyticsruntime information may also include, but is not limited to, estimatedor forecasted application execution duration and their respectiveexecution states (e.g., foreground state, background state, suspendedstate, etc.) for each application estimated or forecasted for executionby the mobile device 102-1 during, after, and/or substantiallycontemporaneously (e.g., within 5 minutes, 10 minutes, 15 minutes, etc.)with the occurrence of one or more analytics location contexts and/oranalytics event contexts.

It may be appreciated that the analytics application context informationmay be utilized by the power analytics prediction component 114-3 toestimate or forecast the likely list of applications that the mobiledevice 102-1 may execute and/or pending to execute for a given contextand/or in response to a device application event. Additionally, theanalytics application context information may also be utilized by thepower analytics prediction component 114-3 to determine the predominantapplications and/or non-predominant applications that are executed for agiven context and/or in response to a device application event based atleast partially on component utilization of the mobile device 102-1(e.g., processing component utilization, etc.).

The power analytics application 109 may further include, but is notlimited to, power analytics prediction component 114-3 configured toreceive generated analytics information, device profile information,and/or optionally, at least a portion of user profile information togenerate predicted information including power curve information 212-4,predicted context information 212-5, predicted power event information212-7, and/or recommendation information including context sensitiverecommendation information 212-6.

In some embodiments, the predicted context information 215-5 mayinclude, but is not limited to, past context information 214-1, futurecontext information 214-2, and/or analytics context information 212-3.The future context information 214-2 may be representative of one ormore future contexts scheduled, planned, or otherwise anticipated tooccur at an approximate time, an approximate location, for anapproximate duration in the future but has not yet occurred. By way ofexample, an exemplary future context may include, but is not limited to,a scheduled meeting at Location D from 9:30 AM until 10:30 AM on Mondaywhen the current time is 8 AM on Monday. The example is not limited inthis context. In some embodiments, the power analytics predictioncomponent 114-3 may be configured to generate the future contextinformation 214-2 representative of one or more future contexts (e.g.,future contexts 362-1, 362-2, 362-3 further discussed with respect toFIG. 3E, etc.) based at least partially on device calendar eventinformation 210-3 representative of one or more device calendar events(e.g., one or more scheduled appoints, meetings, reminders, applicationinstall events, application update events, etc.) and/or optionally, userevent information representative of one or more user events (e.g., oneor more social events, etc.) of the user profile information 210-5. Thegenerated future context information 214-2 may include, but is notlimited to, future location context information, future event contextinformation, and/or future application context information.

The future location context information may be representative of one ormore future location contexts that identify a scheduled, planned, orotherwise anticipated location for a user and consequently, the mobiledevice 102-1 of the user, which may further infer the general activityor activities for the user during a future set time period or intervalon a recurring day of the week. Each future location context may beassociated with a future location context start time, future locationcontext end time, future location context duration, and/or futurelocation category (e.g., home, work, school, traveling, etc.).

The future event context information may be representative of one ormore future events contexts that identify scheduled, planned, orotherwise anticipated device events (e.g., device calendar events suchas a scheduled meeting, etc.) and/or optionally, one or more socialevents (e.g., a scheduled social event represented by user eventinformation, etc.) for the mobile device 102-1 and/or user during afuture set time period or interval on a recurring day of the week. Eachfuture event context may be associated with a future event context starttime, future event context end time, future event context duration,future event category (e.g., calendar event, power event, applicationevent, social event, etc.), future event sub-category associated witheach past event category (e.g., scheduled appointments, meetings, and/orreminders associated with calendar event category, and/or social eventcategory, scheduled battery charge event and/or battery discharge eventassociated with power event category, scheduled application installevent, application uninstall event, and/or application update eventassociated with application event category, etc.).

The future application context information, may be representative of oneor more future application contexts. The one or more future applicationcontext may correspond to and/or be associated with future locationcontext or future event context and provide a list of applications foreach future event context and/or future location context represented bythe future event context information and/or future location contextinformation, respectively, that is estimated or forecasted to beexecuted during, after, or substantially contemporaneously with eachfuture event context and/or future location context by the mobile device102-1. For example, a future application context may correspond to or beassociated with a future event context (e.g., a calendar event such as ascheduled meeting, etc.) to provide an estimated or forecasted lists ofapplications that may be executed during, after, or substantiallycontemporaneously (e.g., within 5 minutes, 10 minutes, 15 minutes, etc.)to the occurrence of that future event context (e.g., the calendar eventsuch as the scheduled meeting, etc.).

In some embodiments, each future application context may also beassociated with future runtime information. The future runtimeinformation may be representative of estimated or forecasted mobiledevice 102-1 component utilization (e.g., processing component 126utilization, etc.) for each application estimated or forecasted forexecution, so that one or more predominant applications (e.g.,applications with the highest processing component 126 utilization,etc.) and/or non-predominant applications utilized may be identified.The future runtime information may also include, but is not limited to,application execution duration and their respective execution states(e.g., foreground state, background state, suspended state, etc.) foreach application that is estimated or forecasted to be executed durationduring, after, and/or substantially contemporaneously (e.g., within 5minutes, 10 minutes, 15 minutes, etc.) with the occurrence of one ormore future location contexts and/or future event contexts.

It may be appreciated that while some future event contexts such as, forexample, calendar events and/or social events associated with thecalendar application 124-1-11 and/or social networking system 101,respectively, are unlikely to list one or more applications 124-1-b thatmay be executed by the mobile device 102-1 during those events (e.g.,calendar events, social events, etc.), the power analytics predictioncomponent 114-3 may determine the estimated or forecasted list ofapplications that may be executed during one or more future locationcontexts and/or future event contexts by matching at least partially afuture location context and/or future event context with analyticslocation context and/or analytics event context (e.g., matching based onthe future location category and/or future event category with analyticslocation category and/or analytics event category, etc.).

To generate the predicted context information 212-5, in someembodiments, the power analytics prediction component 114-3 may beconfigured to replace one or more analytics contexts represented by theanalytics context information 212-3 with one or more future contexts ofthe future context information 214-2 for a set time period or intervalwithin a recurring day of the week. Additionally, for any set timeperiod in the past or that has already occurred, at least a portion ofthe analytics context information 212-3, and/or future contextinformation 214-2 may be replaced with past context information 214-1.

The predicted power curve information 212-4 may be configured to providean estimate or forecast of the power utilization for the mobile device102-1 based at least partially on past power utilization within a settime period or interval and future power utilization within a set timeperiod or interval. In some embodiments, the predicted power curveinformation 212-4 may be generated based at least partially on pastpower curve information 214-3, future power curve information 214-4,and/or analytics power curve information 212-2.

The future power curve information 214-4 may be representative of futureestimated or forecasted power utilization for one or more futurecontexts (e.g., future location contexts, future event contexts, etc.)and/or estimated or forecasted power utilization for one or more deviceapplication events (e.g., application install event, application updateevent, application uninstall event, etc.). In some embodiments, thepower analytics prediction component 114-3 may generate the future powercurve information 214-4 for one or more future contexts, based at leastpartially on an aggregate and/or summation of analytics powerutilization information of the analytics model information 212-1 for oneor more applications 124-1-b (e.g., aggregate or summation of one ormore linear and/or nonlinear functions, etc.) that the mobile device102-1 is estimated or forecasted to execute for an estimated orforecasted duration. The estimated or forecasted applications to executefor an estimated or forecasted duration during a future context (e.g.,future location contexts, future event contexts, etc.) may be determinedbased at least partially on analytics runtime information of theanalytics context information 212-3 for the one or more applications124-1-b generated by the power analytics modeling component 114-2 forthe mobile device 102-1.

By way of example, if a given future location context and/or futureevent context is a scheduled meeting at Location D for 9:30 AM until11:00 AM on Monday, the future application context information mayindicate that the list of applications executed by the mobile device102-1 for a typical meeting at Location D may include audio/videoapplication 124-1-12 (e.g., recording of audio, etc.), managementapplication 124-1-2, e-mail application 124-1-6, calendar application124-1-111, and/or phone application 124-1-5. The power analyticsprediction component 114-3 may generate the future power curveinformation for the meeting at Location D between 9:30 AM until 10:30 AMon Monday based at least partially on an aggregate and/or summation oflinear and/or nonlinear functions associated with the audio/videoapplication 124-1-12 (e.g., recording of audio, etc.), managementapplication 124-1-2, e-mail application 124-1-6, calendar application124-1-111, and/or phone application 124-1-5. The example is not limitedin this context.

In some embodiments, the power analytics prediction component 114-3 mayalso be configured to generate the future power curve information 214-4for one or more device application events (e.g., device applicationinstall event, device application uninstall event, device applicationupdate event, etc.). The future power curve information 214-4 may begenerated for one or more device application events based at leastpartially on analytics information (e.g., analytics application contextinformation of the analytics context information 212-3 corresponding toone or more device applications events, analytics model information212-1, etc.) generated for mobile device 102-1.

It may be appreciated that in instances when a device application eventfor the mobile device 102-1 is an application installation event and/orapplication update event for a newly installed and/or updatedapplication that the mobile device 102-1 has not previously executed(i.e., if the newly installed and/or updated application is executed, itwould be first time the mobile device 102-1 is executing the newlyinstalled and/or updated application), the power analytics predictioncomponent 114-3 may be configured to determine the estimated orforecasted applications that the mobile 102-1 may execute and theduration of that execution after or substantially contemporaneous withthe device application event based at least partially on analyticsinformation (e.g., analytics application context information ofanalytics context information 212-3, analytics model information 212-1,etc.) for other mobile devices (e.g., mobile device 102-2, 102-3, etc.).To ensure that the estimated or forecasted power utilization issubstantially approximate for mobile device 102-1, the analyticsinformation (e.g., analytics context information 212-3, analytics modelinformation 212-1, etc.) for other mobile devices generated by the poweranalytics modeling component 114-2 may be utilized, when the othermobile devices are substantially similar to the mobile device 102-1(e.g., the one or more components of the mobile devices aresubstantially similar or the same, etc.) and/or the other mobile deviceshave executed the newly installed or updated application after orsubstantially contemporaneously with the installation or update of thenewly installed or updated application. This may enable the poweranalytics application 109 to approximately predict the power utilizationof the mobile device 102-1, based on power utilization of other mobiledevices when a new application is installed on the mobile device 120-1.

To more accurately predict the estimated or forecasted powerutilization, the power analytics prediction component 114-3 mayoptionally determine the estimated or forecasted applications that themobile device 102-1 may execute based at least partially on theanalytics information (e.g., analytics context information 212-3,analytics model information 212-1, etc.) for the other mobile devices(e.g., mobile device 102-2, 102-3, etc.), when users of the other mobiledevices are socially connected (e.g., friends, family, etc.) with theuser of mobile device 102-1 based at least partially on user socialconnections information of the user profile information associated withat least one user in the social networking system 101. Additionally, toensure that the predictions are substantially accurate, in someembodiments, the power analytics prediction component 114-3 may furtherdetermine estimated or forecasted applications executed by the mobiledevice 102-1, based on analytics information of the other mobile devicesthat are substantially similar to mobile device 102-1 (e.g., the one ormore components of the mobile devices are substantially similar or thesame, etc.), and/or analytics information of the other mobile deviceshave executed the newly installed or updated application after orsubstantially contemporaneously with the installation or update of thenew application. This may enable the power analytics application 109 toimprove prediction of the power utilization of the mobile device 102-1,based on power utilization of other mobile devices when a newapplication is installed on the mobile devices and the users of othermobile devices are friends of the user of mobile device 102-1 presumethat the user's actions on the mobile device 102-1 are more likely to besimilar to those of his/her friends, family, and the like rather thanstrangers.

In some embodiments, the power analytics prediction component 114-3 maybe configured to generate predicted power curve information 212-4 basedat least partially on analytics power curve information 212-2, futurepower curve information 214-3, and/or past power curve information 214-3further discussed with respect FIG. 3D-3F.

The predicted power event information 212-7 may be configured to provideone or more predicted threshold limit events (e.g., predicted thresholdlimit event 352-1 further discussed with respect to FIG. 3D, etc.)and/or one or more predicted charge events (e.g., predicted charge event350-1 further discussed with respect to FIG. 3D, etc.). The predictedthreshold limit events, represented by predicted threshold limit eventinformation, may provide an estimate or forecast of the approximate timeand approximate power reserve the mobile device 102-1 may fall below apredetermined threshold (e.g., power reserve threshold limit 344 furtherdiscussed with respect to FIG. 3D-3F, etc.). The predicted chargeevents, represented by predicted charge event information, may providean approximate time and power reserve the battery 188 of the mobiledevice 102-1 may be charged by the user. In some embodiments, thepredicted power curve information 212-4, may include and/or beassociated with one or more predicted threshold limit events (e.g.,predicted threshold limit event 352-1 further discussed with respect toFIG. 3D, etc.) and/or one or more predicted charge events (e.g.,predicted charge events 350-1 further discussed with respect to FIG. 3D,etc.). The power analytics prediction component 114-3 may generatepredicted power event information 212-7 based at least partially on thegenerated predicted power curve information 212-4, predicted contextinformation 212-5, analytics power curve information 212-2, analyticscontext information 212-3, and/or power reserve threshold limitinformation of the mobile power application preferences information (notshown).

The power analytics prediction component 114-3 may be further configuredto generate context sensitive recommendations information 212-6 forproviding one or more context sensitive recommendations corresponding toone or more predicted contexts to the mobile device 102-1 for visualpresentation on a display screen of the mobile device 102-1. In someembodiments, the power analytics prediction component 114-3 may beconfigured to provide context sensitive recommendations, when predictedpower event information 212-7 indicates that a predicted thresh holdlimit event that the power reserve for the mobile device 102-1 will fallbelow a predetermined threshold (e.g., power reserve threshold limit 344further discussed with respect to FIG. 3D-3F) before the predictedcharge event in a set time period or interval on a reoccurring day ofthe week. Moreover, based at least partially on the predicted contextbefore the estimated or forecasted time of the predicted threshold limitevent, the power analytics prediction component 114-3 may be configuredto generate one or more context sensitive recommendations based at leastpartially on the predicted contexts.

In some embodiments, the context sensitive recommendation may include,one or more context sensitive application recommendations, contextsensitive component recommendations, and/or context sensitive powerrecommendations. The context sensitive application recommendations maybe visually presented to recommend to close and/or terminate one or morenon-predominant applications executing in a foreground state, backgroundstate, or pending execution in a suspended state based at leastpartially on predicted context information. This may enable users tocontinue to use the predominant application (e.g., continuing to uselocation application 124-1-10 for navigation while traveling betweenlocations, continuing to use audio/video application 124-1-12 forrecording during a meeting, etc.) in a given context while reducingoverall power utilization of the mobile device 102-1 by closing orterminating unnecessary applications. Additionally, the contextsensitive application recommendations may also be visually presented torecommend not launching one or more applications 124-1-b having highpower utilization, disabling one or more application specific featuresfor one or more applications 124-1-b, configuring one or moreapplications 124-1-b to a low power state, or any other recommendationthat may assist the user in reducing power consumption. Moreover, thepower analytics prediction component 114-3 may be configured todetermine the one or more high power utilization applications based atleast partially on a comparison of one or more linear and/or nonlinearfunctions representative of power utilization of one or moreapplications 124-1-b represented by the analytics application modelinformation.

The context sensitive component recommendations may be visuallypresented to recommend the user to configure one or more components to alow power state or disabled state based at least partially on thecontext sensitive application recommendations and/or predicted contextinformation. Moreover, the power analytics prediction component 114-3may be configured to determine which components utilized bynon-predominant applications may be configured to operate in a low powerstate or disabled state without disabling or preventing the use of oneor more predominant applications.

By way of example, the context sensitive component recommendation duringa meeting may include, but is not limited to, disabling at least aportion of the communications component 158, acceleration component 180,haptic component 172, when the predominant application utilized duringthe meeting is audio/video application 124-1-12. In another example, thecontext sensitive component recommendation during traveling may include,but is not limited to, placing the touch sensitive display component 182in a low power state by reducing the display screen brightness, when thepredominant application utilized during traveling is location component124-1-10.

The context sensitive power recommendations may be visually presentedrecommend charging the mobile device 102-1 and/or configuring the mobiledevice 102-1 to a low power state (e.g., disabling one or morecomponents of the mobile device 102-1 and/or terminating one or moreapplications 124-1-b executing or pending for execution on the mobiledevice 102-1) or disabled state (e.g., turned off, etc.) based at leastpartially on predicted context information. Moreover, the poweranalytics prediction component 114-3 may be configured to identify oneor more charging opportunities based at least partially on predictedcontext information and/or predicted power curve information. This mayenable the power analytics prediction component 114-3 to generatecontext sensitive power recommendations that may recommend the user tocharge the mobile device 102-1, when the predicted context information215-5 indicates that charging the mobile device practical. Additionallyor alternatively, the context sensitive power recommendation may alsorecommend the user to configure the mobile device to a low power state(e.g., reduced processor component 126 frequency, etc.) or a disabledstate.

It may be appreciated that, in addition to visually presenting the oneor more context sensitive recommendations on a display screen, any ofthe context sensitive recommendation information may also be automaticimplemented by the mobile power application 124-1-1. For example, themobile power application 124-1-1 may automatically terminate one or morenon-predominant applications or automatically reduce the brightness ofthe display screen of the mobile device 102-1 during one or morecontexts based at least partially on the one or more context sensitiverecommendations during the respective contexts. The example is notlimited in this context.

FIG. 3A illustrates exemplary embodiment of past power curve information214-3. As illustrated in FIG. 3A, the past power curves 302-1, 302-2,302-3 may be represented by past power curve information 214-3. Eachpast power curve (e.g., past power curve 302-1, 302-2, 302-3) may berepresentative of a power reserve vs time curve for a set time period orinterval of time (e.g., 24 hours) starting at time T (e.g., 12:00 AM),and continuing until T+n (e.g., 11:59 PM). Moreover, the past powercurves 302-1, 302-2, 302-3 may be representative of the powerutilization starting at 12:00 AM for the past three Mondays in the pastthree weeks. It may be appreciated while only three past power curves302-1, 302-2, 302-3 are illustrated, the past power curve information214-3 may be representative of any number of past power curves as moredevice profile information and/or optionally user profile information210-5 are received from mobile device 102-1. The past power curves302-1, 302-2, 302-3 may also be associated with past contextsrepresented by past context information 214-1 such as, for example, pastevent contexts 304-1, 304-2, 304-3, respectively, indicating batterycharge events regarding when the mobile device 102-1 was starting to becharged on Mondays.

FIG. 3B illustrates exemplary embodiment of past context information214-1. As illustrated in FIG. 3B the past contexts 312-1, 312-2, 312-3may be represented by past context information 214-1. Each set of pastcontexts may be representative of one or more past contexts (e.g.,activities and/or locations, etc.) for a set time period or interval oftime (e.g., 24 hours) starting at time T (12:00 AM), and continuinguntil T+n (e.g., 11:59 PM). Moreover, the set of past contexts 312-1,312-2, 312-3 may be representative of the past device events, pastlocations, and/or past social events associated with the user of thedevice 102-1 and/or the mobile device 102-1, starting at time T (12:00AM) for the past three Mondays in the past three weeks. It may beappreciated that while only three set of past contexts 302-1, 302-2,302-3 are shown, the past context information 214-1 may berepresentative of any number of sets of past contexts past power curvesas more device profile information and/or optionally user profileinformation 210-5 are received from mobile device 102-1 for each day ofthe one or more weeks. Each set of past contexts may also include, butis not limited to one or more past location contexts (e.g., location A,location B, location C, traveling from location A to location B, etc.)represented by past location context information, one or more past eventcontexts (e.g., home, work, meeting, battery charge event, etc.)represented by past event context information, and/or one or more pastapplication contexts (not shown) corresponding to and/or associated withthe one or more past location contexts and/or past event contexts.

As further illustrated in FIG. 3B, each past location context may havevarying past location start time, past location context end time, pastlocation context duration, and/or past location category (e.g., home,etc.). Similarly, each past event context may also have varying pastevent context start time, past event context end time, past eventcontext duration, past event category (e.g., calendar event, etc.),and/or past event sub-category associated with each past event category(e.g., meeting, etc.).

It may be appreciated that in order to improve clarity and/orunderstanding of the operating environments, some past contexts, futurecontexts, and/or analytics contexts, (e.g., past, future, and/oranalytics event contexts for battery charge event, battery dischargeevent, application install event, application update event, applicationuninstalled event, etc.) that typically span a duration of severalminutes to several hours, may not be illustrated or if illustrated mayhave a short duration or without any duration.

FIG. 3C illustrates exemplary embodiment of analytics information (e.g.,analytics context information 212-3 and analytics power curveinformation 212-2, etc.). As illustrated in FIG. 3C the analytics powercurve 322 is represented by the analytics power curve information 212-2and generated by the power analytics modeling component 114-2 based atleast partially on past power curve information 214-3 representative ofone or more past power curves (e.g., power curves 302-1, 302-2, 302-3).Additionally, the analytics contexts 326 represented by analyticscontext information 212-3 and generated based at least partially on oneor more past contexts (e.g., past sets of contexts 312-1, 312-2, 312-3)represented by past context information 214-1. Furthermore, theanalytics power curve 322 may be further associated with an analyticsevent context and in particular, analytics charge event context 324representative of an estimated or forecasted time of when the battery188 of mobile device 102-1 is likely to be charged by the user.

FIG. 3D illustrates a first exemplary operating environment 340 ofpredicted information and/or recommendation information for a particularday of the week (e.g., Monday) with the current time being T+13 (1:00PM). As illustrated in operating environment 340 of FIG. 3D, thepredicted contexts 341-1 represented by predicted context information215-5 may be generated and/or may include one or more past contexts342-1 represented by past context information 214-1 and/or one or moreanalytics contexts represented by analytics context information 212-3.Additionally, the predicted power curve 348-1 may be represented bypredicted power curve information 212-4 may be generated based at leastpartially on at least a portion of the past power curve information214-3 (e.g., representative of the past power curve shown in solidlines) and/or analytics power curve information 212-2 (e.g.,representative of analytics power curve shown in dashed lines).

With continued reference to operating environment 340 of FIG. 3D, atleast a portion of the past power curve (shown in solid lines) andrepresented by past power curve information 214-3 may substantiallycorrespond to and/or be associated with one or more past contexts 342-1.The past power curve (shown in solid lines) may substantially correspondto one or more past contexts 342-1 and may be representative of thepower utilization of mobile device 102-1 during various past contexts342-1 starting from time T (12:00 AM) and ending at time T+13 (1:00 PM),which is also the current time. Further, as illustrated between timeT+12 (12:00 PM) and T+13 (1:00 PM), the past power curve portion of thepredicted power curve 348-1 indicates that the mobile device 102-1substantially deviated (e.g., greater than or equal to approximately 10%deviation, etc.) from estimated or forecasted power utilization asrepresented by analytics power curve 322 during the same time period orinterval, which may be a result of intensive use of mobile device 102-1(e.g., intensive use of one or more applications 124-1-b and/or one ormore components of mobile device 102-1, etc.).

With continued reference to operating environment 340 of FIG. 3D, atleast a portion of the predicted power curve 348-1 may also include, butis not limited to, a translated version of the analytics power curve322. The translated version of the analytics power curve 322 maysubstantially correspond to and/or be associated with the analyticscontexts 345-1 and may represent estimated or forecasted powerutilization of mobile device 102-1 during analytics contexts 345-1starting from time T+12 (12:00 PM) and ending at time T+n for a typicalMonday. It may be appreciated that because the past power curve (shownin solid lines) represents the past power utilization and the actualremaining power reserve of the mobile device 102-1 up to and includingthe time T+13 (1:00 PM), the analytics power curve 322 starting at timeT+13 (1:00 PM) may be appropriately translated (in a linear and/ornon-linear fashion) based at least partially on the remaining powerreserve at time T+12 (12:00 PM). The translated analytics power curve(shown in dashed lines in predicted power curve 348-1) may represent thepower utilization for the remaining power reserve of the mobile device102-1 given the amount of power reserve remaining for use.

With continued reference to operating environment 340 of FIG. 3D, thepower analytics prediction component 114-3 may generate the predictedcontexts 341-1, which may be represented by the predicted contextinformation 212-5, by replacing analytics contexts with past contexts342-1 corresponding to a time period or interval starting from time T(12:00 AM) and ending at current time T+13 (1:00 PM).

The power analytics prediction component 114-3 may generate thepredicted power curve 348-1 represented by predicted power curveinformation 212-4 by replacing the analytics power curve 322 representedby analytics power curve information 212-2 corresponding to the timeperiod or interval starting at time T (12:00 AM) and ending at currenttime T+13 (1:00 PM). The power analytics prediction component 114-3 mayalso replace portions of the analytics power curve 322 starting atcurrent time T+13 (1:00 PM), et and ending at time T+n with translatedanalytics power curve (shown in predicted power curve 348-1 as dashedlines). Effectively, the predicted power curve 348-1 may berepresentative of an estimated or forecasted power utilization of themobile device 102-1 for this particular Monday based at least partiallyon the past power utilization between time T and current time T+13 (1:00PM) for this particular Monday and estimated or predicted powerutilization generated based at least partially on one or more pastMonday's.

With continued reference to operating environment 340 of FIG. 3D andbased at least partially on the predicted power curve 348-1, analyticscharge event context 324, power reserve threshold limit 344, and/orpredicted contexts 341-1, the power analytics prediction component 114-3may determine the predicted power event information 212-7 which mayinclude, but is not limited to, predicted threshold limit event 352-1and predicted charge event 350-1. The predicted threshold limit event352-1 may provide the estimated or forecasted time the power reserve formobile device 102-1 will fall below a power reserve threshold limit 344and predicted charge event 350-1 may provide estimated or forecastedtime and power reserve the mobile device 102-1 will likely charged. Whenthe estimated or forecasted time for the predicted threshold limit event352-1 occurs substantially before (e.g., more than 5 minutes, 10minutes, 15 minutes, etc.) the estimated or forecasted time for thepredicted charge event 350-1, the power analytics prediction component114-3 may generate and/or provide context sensitive recommendationsrepresented by context sensitive recommendation information 212-6 forone or more context sensitive recommendation periods 346-1 and 346-2.

As illustrated in operating environment 340 of FIG. 3D, the contextsensitive recommendation period 346-1 may substantially correspond toanalytics location context for traveling from location B to location C.Similarly, the context sensitive recommendation period 346-2 maysubstantially correspond to analytics location context for work atLocation C and analytics event context for a meeting.

The analytics location context for traveling may be associated withanalytics application context (not shown), which may indicate that thepredominant application executed during traveling is the locationapplication 124-1-10 for providing GPS navigation. As such, the poweranalytics prediction component 114-3 may provide one or more contextsensitive application recommendations to the mobile device 102-1 forcontext sensitive recommendation period 346-1 to reduce powerutilization during the analytics location context for traveling (e.g.traveling from location B to location C). The one or more contextsensitive application recommendations may include one or more contextsensitive application recommendations, one or more context sensitivecomponent recommendations, and/or one or more context sensitive powerrecommendations.

The one or more context sensitive application recommendations forcontext sensitive recommendation period 346-1 may include, but is notlimited to, closing and/or terminating one or more non-predominantapplications (e.g., applications not including location application124-1-10, etc.), refrain from launching one or more processing componentintensive applications (e.g., refrain from using entertainmentapplication 124-1-7 such as Angry Birds®, etc.), configuring one or morepredominant and/or non-predominant applications to a low power state(e.g., turning off push e-mail services for e-mail application 124-1-6or turning off push notifications for social application 124-1-9 such asFacebook®, etc.)

The one or more context sensitive component recommendations for contextsensitive recommendation period 346-1 may include, but is not limitedto, configuring one or more components of the mobile device 102-1 notutilized by the predominant application (i.e., location application124-1-10) to a low power state (e.g., reducing the brightness of thetouch sensitive display component 182, etc.) or to a disabled powerstate (e.g., disabling image capture component 154, haptic component172, acceleration component 180 which may not be utilized by thelocation application 124-1-10, etc.).

The one or more context sensitive power recommendations for contextsensitive recommendation period 346-1 may include, but is not limitedto, configuring the mobile device to a low power state (e.g., reducingprocessing component 126 operating frequency, etc.) However, it may beappreciated that power analytics prediction component 114-3 may notrecommend the user to charge the mobile device 102-1 because it would inconsistent with the analytics location context for traveling because theuser may not have the opportunity to charge the battery 188 of themobile device 102-1 while traveling.

Similarly, the power analytics prediction component 114-3 may alsoprovide one or more context sensitive application recommendations (e.g.,context sensitive application recommendations, context sensitivecomponent recommendations, and/or context sensitive powerrecommendations, etc.) to the mobile device 102-1 for context sensitiverecommendation period 346-2 to reduce power utilization during theanalytics location context for meeting at work (e.g. meeting at work atlocation C). The associated analytics application contexts (not shown)may identify that the predominant application executed during themeeting is audio/video application 124-1-12 for recording audio and thepredominant application executed during the location C for work ise-mail application 124-1-6 for sending and receiving e-mail.

The one or more context sensitive application recommendations forcontext sensitive recommendation period 346-2 may include, but is notlimited to, closing and/or terminating one or more non-predominantapplications (e.g., applications not including e-mail application124-1-6 and audio/video application 124-1-12, etc.), refrain fromlaunching one or more processing component intensive applications (e.g.,refrain from using entertainment application 124-1-7 such as AngryBirds®, etc.), configuring one or more predominant and/ornon-predominant applications to a low power state (e.g., turning offpush e-mail services for e-mail application 124-1-6 or turning off pushnotifications for social application 124-1-9 such as Facebook®, etc.)

The one or more context sensitive component recommendations for contextsensitive recommendation period 346-2 may include, but is not limitedto, configuring one or more components of the mobile device 102-1 notutilized by the predominant applications (i.e., audio/video application124-1-12 for recording audio and e-mail application 124-1-6 for sendingand receiving e-mail) to a low power state (e.g., reducing thebrightness of the touch sensitive display component 182, etc.) or to adisabled power state (e.g., disabling image capture component 154,haptic component 172, acceleration component 180, location component 176which may not be utilized by audio/video application 124-1-12 and e-mailapplication 124-1-6, etc.).

The one or more context sensitive power recommendations for contextsensitive recommendation period 346-2 may include, but is not limitedto, configuring the mobile device to a low power state (e.g., reducingprocessing component 126 operating frequency, etc.) and to charge themobile device 102-1.

FIG. 3E illustrates a second exemplary operating environment 360 ofpredicted information and/or recommendation information for a particularday of the week (e.g., Monday) with the current time being approximatelyT+8.5 (8:30 AM). As illustrated in operating environment 360 of FIG. 3E,the predicted contexts 341-2 represented by predicted contextinformation 212-5 may be generated and/or may include one or more pastcontexts 342-2 represented by past context information 214-1, one ormore future contexts 362-1, 362-2, 362-3 and/or one or more analyticscontexts represented by analytics context information 212-3.Additionally, the predicted power curve 348-2 may be represented bypredicted power curve information 212-4 may be generated based at leastpartially on at least a portion of the past power curve information214-3 (e.g., representative of the past power curve shown in solidlines), future power curve information 214-4, and/or analytics powercurve information 212-2 (e.g., representative of analytics power curveshown in dashed lines).

With continued reference to operating environment 360 of FIG. 3E, atleast a portion of the predicted power curve 348-2 may include the pastpower curve (shown in solid lines) and represented by past power curveinformation 214-3. The past power curve may substantially correspond toand/or be associated with the past contexts 342-2 and may represent thepower utilization of mobile device 102-1 during past contexts 342-2 fromtime T (12:00 AM) to current time T+8.5 (8:30 AM).

With continued reference to operating environment 360 of FIG. 3E, atleast a portion of the predicted power curve 348-2 may also include, butis not limited to, a future power curve (shown in dot dashed lines)represented by future power curve information 214-4. The future powercurve may substantially correspond to and/or be associated with one ormore future contexts 362-1, 362-2, 362-3, represented by future contextinformation 214-2. By way of example, the future contexts 362-2 mayrepresent a future location context and a future event context. Thefuture event context may correspond to a scheduled meeting at time T+9.5(9:30 AM) and ending at time T+11 (11:00 AM) and the future locationcontext may correspond to location D. The future context 362-1 mayrepresent a future location context for traveling from at location A tolocation D and the future context 362-3 may represent a future locationcontext for traveling from location D to work location B.

The future power curve (shown in dot dashed lines) corresponding to eachfuture contexts 362-1, 362-2, 362-3 may represent estimated or predictedpower utilization of the mobile device 102-1 during a typical meeting(e.g., meeting at location D) and typical traveling (e.g., travelingfrom location A to location D and traveling from location D to locationB), which may be determined by the power analytics prediction component114-3 based at least partially on future application context informationand analytics model information 212-1 for each application that isestimated or forecasted to be executed during the future contexts 362-1,362-2, 362-3. It may be appreciated that because the past power curve(shown in solid lines) represents the past power utilization andremaining power reserve of the mobile device 102-1 up to and includingthe current time (e.g., T+8.5 (8:30 AM), etc.), the future power curvemay be appropriately translated (in a linear and/or non-linear fashion)based at least partially on the remaining power reserve at current time(e.g., T+8.5 (8:30 AM), etc.).

With continued reference to operating environment 360 of FIG. 3E, atleast a portion of the predicted power curve 348-2 may also include, butis not limited to, a translated version of the analytics power curve322. The translated version of the analytics power curve 322 maysubstantially correspond to and/or be associated with the analyticscontexts 345-2 and may represent the power utilization of mobile device102-1 during analytics contexts 345-2 from time T+12 (12:00 PM) andending at time T+n. It may be appreciated that because the future powercurve (shown in dot dashed lines) represents the future powerutilization and estimated or forecasted remaining power reserve of themobile device 102-1 up to and including the time T+12 (12:00 PM), theanalytics power curve 322 starting at time T+12 (12:00 PM) may beappropriately translated (in a linear and/or non-linear fashion) basedat least partially on the remaining power reserve at time T+12 (12:00PM).

The power analytics prediction component 114-3 may generate thepredicted contexts 341-2, which may be represented by the predictedcontext information 212-5, by replacing analytics contexts 345-2starting at time T and ending at time T+n with future analytics contextsat the respective time periods or intervals (e.g., replacing analyticscontext between 9:30 AM and 11:00 AM with future contexts 362-2 for ascheduled meeting between 9:30 AM and 11 AM at location D). The poweranalytics prediction component 114-3 may also replace analytics contexts345-2 and/or future contexts 362-1, 362-2, 362-3 (if any), starting attime T and ending at time T+n with past contexts 342-2 corresponding toa time period or interval from a past time to the current time (e.g.,from T (12:00 AM) to time T+8.5 (8:30 AM), etc.). Additionally, based atleast partially on one or more contexts (e.g., past context 342-2, andanalytics contexts 345-2, and future contexts 362-2) that may beadjacent to the future contexts 362-1, 362-3, the power analyticsprediction component 114-3 may further determine that the future context362-1 may represent the future location context for traveling from atlocation A to location D and the future context 362-3 may represent afuture location context for traveling from location D to work locationB.

The power analytics prediction component 114-3 may generate thepredicted power curve 348-1 represented by predicted power curveinformation 212-4 by replacing the analytics power curve 322 (shown indashed lines) represented by analytics power curve information 212-2starting at time T (12:00 AM) and ending at time T+8.5 (8:30 AM) withpast power curve (shown in solid lines) represented by past power curveinformation 214-3 starting at time T (12:00 AM) up to the current time(e.g., T+8.5 (8:30 AM), etc.). The power analytics prediction component114-3 may also replace portions of the analytics power curve 322 withfuture power curve (shown in dot dash lines) starting at current time(e.g., T+8.5 (8:30 AM), etc.) and ending at estimated or forecasted time(e.g., T+12 (12:00 PM), etc.) based at least partially on theapproximate duration of future contexts 362-1, 362-2, 362-3.Furthermore, the power analytics prediction component 114-3 may alsoreplace portions of the analytics power curve 322 starting at estimatedor forecasted time (e.g., T+12 (12:00 PM), etc.) and ending at time T+nwith translated analytics power curve (shown in predicted power curve348-2 as dashed lines). Effectively, the predicted power curve 348-2 maybe representative of an estimated or forecasted power utilization of themobile device 102-1 for this particular Monday based at least partiallyon the past power utilization between time T and current time T+8.5(8:30 AM) for this particular Monday, estimated or forecasted powerutilization for a scheduled meeting starting at time T+9.5 (9:30 AM) andending at time T+11 (11:00 AM) and traveling to and from the scheduledmeeting at location D, and estimated or forecasted power utilizationgenerated based at least partially on one or more past Monday's.

With continued reference to operating environment 360 of FIG. 3E andbased at least partially on the predicted power curve 348-1, analyticscharge event context 324, power reserve threshold limit 344, and/orpredicted contexts 341-1, the power analytics prediction component 114-3may determine the predicted power event information 212-7 which mayinclude, but is not limited to, predicted threshold limit event 352-2representative of the estimated or forested time and power reserve ofthe mobile device will fall below the power reserve threshold limit 344and predicted charge event 350-2 representative of the estimated orforecasted time and power reserve the mobile device 102-1 will likelycharged. When the estimated or forecasted time for the predictedthreshold limit event 352-2 occurs substantially before (e.g., more than5 minutes, 10 minutes, 15 minutes, etc.) the estimated or forecastedtime for the predicted charge event 350-2, the power analyticsprediction component 114-3 may generate and/or provide context sensitiverecommendations (not shown) represented by context sensitiverecommendation information 212-6 for one or more context sensitiverecommendation periods 364-1, 364-2, 364-3, 364-4, 364-5 correspondingone or more future contexts 362-1, 362-2, 362-3 and on or more analyticscontexts 345-2 during any time before the estimated or forecasted timeassociated with the predicted threshold limit event 352-2.

In the operating environment 360 of FIG. 3E, the context sensitiverecommendation period 364-1 and 364-3 may substantially correspond tofuture location context for traveling from location A to location D andlocation D to location B (not shown). Similarly, the context sensitiverecommendation period 364-5 may substantially correspond to analyticslocation context for traveling from location B to location C.Additionally, the context sensitive recommendation period 364-4 maysubstantially correspond to analytics location context for work atlocation B and the context sensitive recommendation period 364-2 maysubstantially correspond to future location context at location D and afuture event context for a scheduled meeting between 9:30 AM and 11:00AM (not shown).

Assuming that the predominant application estimated or forecasted to beexecuted during analytics location context and/or future locationcontexts for traveling between locations is the location application124-1-10, the power analytics prediction component 114-3 may provide oneor more context sensitive recommendations represented by contextsensitive recommendation information 212-6 for future location contexts362-1, 362-3 for traveling from location A to location D and travelingfrom location D to location B, and analytics location context fortraveling from location B to location C. The one or more contextsensitive recommendations may include context sensitive applicationrecommendations (e.g., recommendation to close and/or terminate one ormore non-predominant applications, etc.), context sensitive componentrecommendations (e.g., recommendation to configure one or morecomponents of the mobile device 102-1, not utilized by the predominantapplication to a low power state or to a disabled power state, etc.),and context sensitive power recommendations (e.g., recommendation toconfigure the mobile device 102-1 to a low power state, etc.).

Similarly, assuming that the predominant applications estimated orforecasted to be executed during analytics location context for work atlocation B is the e-mail application 124-1-6 and the predominantapplication estimated or forecasted to be executed during futurelocation context and future meeting context are the e-mail application124-1-6 and the audio/video application 124-1-12. The one or morecontext sensitive recommendations for contexts may include contextsensitive application recommendations (e.g., recommendation to closeand/or terminate one or more non-predominant applications, etc.),context sensitive component recommendations (e.g., recommendation toconfigure one or more components of the mobile device 102-1, notutilized by the predominant application to a low power state or to adisabled power state, etc.), and context sensitive power recommendations(e.g., recommendation to configure the mobile device 102-1 to a lowpower state and charging the mobile device 102-1 etc.).

FIG. 3F illustrates a third exemplary operating environment 380 ofpredicted information and/or recommendation information for a particularday of the week (e.g., Monday) with the current time being approximatelyT+12 (12:00 PM). As illustrated in operating environment 380 of FIG. 3F,the predicted contexts 341-2 represented by predicted contextinformation 212-5 may be generated and/or may include one or more pastcontexts 342-3 represented by past context information 214-1 and/or oneor more analytics contexts represented by analytics context information212-3. Additionally, the predicted power curve 348-3 may be representedby predicted power curve information 212-3 may be generated based atleast partially on at least a portion of the past power curveinformation 214-3 (e.g., representative of the past power curve shown insolid lines), future power curve information 214-4 (e.g., representativeof future power curve shown in dot dashed lines), and/or analytics powercurve information 212-2 (e.g., representative of analytics power curveshown in dashed lines).

With continued reference to operating environment 380 of FIG. 3F, atleast a portion of the predicted power curve 348-3 may include the pastpower curve (shown in solid lines) and represented by past power curveinformation 214-3. The past power curve may substantially correspond toand/or be associated with the past contexts 342-3 and may represent thepower utilization of mobile device 102-1 during past contexts 342-3 fromtime T (12:00 AM) to current time T+12 (12:00 PM).

With continued reference to operating environment 380 of FIG. 3F, atleast a portion of the predicted power curve 348-2 may also include, butis not limited to, a future power curve (shown in dot dashed lines)represented by future power curve information 214-4. The future powercurve may substantially correspond to and/or be associated with deviceevent 384, represented by device events information 210-3. By way ofexample, the device event 384 may represent a device application eventsuch as device application install event for installation of anapplication (e.g., entertainment application 124-1-7 such as AngryBirds®).

The future power curve (shown in dot dashed lines) corresponding todevice event 384 and analytics contexts 345-3 (e.g., analytic contextfor work at location B between time T+12 (12:00 PM) and time T+13 (1:00PM)) may represent estimated or predicted power utilization of themobile device 102-1 and duration of that power utilization after thedevice event 384, which may represent a device application event such asdevice application install event for installation of an application(e.g., installation of entertainment application 124-1-7 such as AngryBirds®). The future power curve corresponding to the device event 384 amay be determined by the power analytics prediction component 114-3based at least partially on analytics information (e.g., analyticsapplication context information of the analytics context information212-3 corresponding to one or more device applications events, analyticsmodel information 212-1) for mobile device 102-1. Additionally oralternatively, for any device events such as device application installevent for installation of an application that has never been executed onthe mobile device 102-1, the future power curve corresponding to thedevice event 384 may be determined by the power analytics predictioncomponent 114-3 based at least partially on analytics information forother mobile devices as previously discussed with respect to FIG. 2. Itmay be appreciated that because the past power curve (shown in solidlines) represents the past power utilization and remaining power reserveof the mobile device 102-1 up to and including the current time (e.g.,T+12 (12:00 PM), etc.), the future power curve corresponding to deviceevent 384 may be appropriately translated (in a linear and/or non-linearfashion) based at least partially on the remaining power reserve atcurrent time (e.g., T+12 (12:00 PM), etc.).

With continued reference to operating environment 380 of FIG. 3F, atleast a portion of the predicted power curve 348-3 may also include, butis not limited to, a translated version of the analytics power curve322. The translated version of the analytics power curve 322 maysubstantially correspond to and/or be associated with the analyticscontexts 345-3 and may represent the power utilization of mobile device102-1 during analytics contexts 345-3 from time T+13 (1:00 PM) andending at time T+n. It may be appreciated that because the future powercurve (shown in dot dashed lines) represents the future powerutilization and estimated or forecasted remaining power reserve of themobile device 102-1 up to and including the time T+13 (1:00 PM), theanalytics power curve 322 starting at time T+13 (1:00 PM) may beappropriately translated (in a linear and/or non-linear fashion) basedat least partially on the remaining power reserve at time T+13 (1:00PM).

The power analytics prediction component 114-3 may generate thepredicted contexts 341-3, which may be represented by the predictedcontext information 212-5, by replacing analytics contexts 345-3starting at time T and ending at time T+n with past contexts 342-3corresponding to a time period or interval from a past time to thecurrent time (e.g., from T (12:00 AM) to time T+12 (12:00 PM), etc.).

The power analytics prediction component 114-3 may generate thepredicted power curve 348-1 represented by predicted power curveinformation 212-4 by replacing the analytics power curve 322 (shown indashed lines) represented by analytics power curve information 212-2starting at time T (12:00 AM) and ending at the current time (e.g., T+12(12:00 PM), etc.) with past power curve (shown in solid lines)represented by past power curve information 214-3 starting at time T(12:00 AM) up to the current time (e.g., T+12 (12:00 PM), etc.). Thepower analytics prediction component 114-3 may also replace portions ofthe analytics power curve 322 with future power curve (shown in dot dashlines) starting at current time (e.g., T+12 (12:00 PM), etc.) and endingat estimated or forecasted ending time (e.g., T+12 (1:00 PM), etc.)).Furthermore, the power analytics prediction component 114-3 may alsoreplace portions of the analytics power curve 322 starting at estimatedor forecasted time (e.g., T+13 (1:00 PM), etc.) and ending at time T+nwith translated analytics power curve (shown in predicted power curve348-2 as dashed lines) starting at the estimated or forecasted time andending at time T+n. Effectively, the predicted power curve 348-3 may berepresentative of an estimated or forecasted power utilization of themobile device 102-1 for this particular Monday based at least partiallyon the past power utilization between time T and current time T+12(12:00 PM) for this particular Monday, estimated or forecasted powerutilization for the mobile device 102-1 after a device event 384 occurssuch as a device application install event for the installation of a newapplication (e.g., newly installed entertainment application 124-1-7such as Angry Birds®, etc.), and estimated or forecasted powerutilization generated based at least partially on one or more pastMonday's.

With continued reference to operating environment 380 of FIG. 3F andbased at least partially on the predicted power curve 348-3, analyticscharge event context 34, power reserve threshold limit 344, and/orpredicted contexts 341-3, the power analytics prediction component 114-3may determine the predicted power event information 212-7 which mayinclude, but is not limited to, predicted threshold limit event 352-3representative of the estimated or forested time and power reserve ofthe mobile device will fall below the power reserve threshold limit 344and predicted charge event 350-3 representative of estimated orforecasted time and power reserve the mobile device 102-1 will likely becharged. When the estimated or forecasted time for the predictedthreshold limit event 352-3 occurs substantially before (e.g., more than5 minutes, 10 minutes, 15 minutes, etc.) the estimated or forecastedtime for the predicted charge event 350-3, the power analyticsprediction component 114-3 may generate and/or provide context sensitiverecommendations (not shown) represented by context sensitiverecommendation information 212-6 for one or more context sensitiverecommendation periods 381-1, 381-2, 381-3 corresponding one or moreanalytics contexts 345-3 during any time before the estimated orforecasted time associated with the predicted threshold limit event352-3.

In the operating environment 380 of FIG. 3F, the context sensitiverecommendation period 381-1 may substantially correspond to analyticlocation context for work at location B. Similarly, the contextsensitive recommendation period 381-2 may substantially correspond toanalytics location context for traveling from location B to location C.Additionally, the context sensitive recommendation period 382-3 maysubstantially correspond to analytics event context and analyticslocation context for a meeting at location C.

Assuming that the predominant application estimated or forecasted to beexecuted for context sensitive recommendation period 381-1 is the e-mailapplication 124-1-6, the power analytics prediction component 114-3 mayprovide one or more context sensitive recommendations represented bycontext sensitive recommendation information 212-6. The one or morecontext sensitive recommendations may include context sensitiveapplication recommendations (e.g., recommendation to close and/orterminate one or more non-predominant applications, recommendation torefrain from launching the newly installed application, etc.), contextsensitive component recommendations (e.g., recommendation to configureone or more components of the mobile device 102-1, not utilized by thepredominant application to a low power state or to a disabled powerstate, etc.), and context sensitive power recommendations (e.g.,recommendation to configure the mobile device 102-1 to a low power stateor charge the mobile device, etc.).

Similarly, assuming that the predominant applications estimated orforecasted to be executed for context sensitive recommendation period381-2 is the location application 124-1-10 and the predominantapplication estimated or forecasted to be executed for context sensitiverecommendation period 381-2 are the e-mail application 124-1-6 and theaudio/video application 124-1-12, the power analytics predictioncomponent 114-3 may provide one or more context sensitiverecommendations represented by context sensitive recommendationinformation 212-6. The one or more context sensitive recommendations forcontexts may include context sensitive application recommendations(e.g., recommendation to close and/or terminate one or morenon-predominant applications, etc.), context sensitive componentrecommendations (e.g., recommendation to configure one or morecomponents of the mobile device 102-1, not utilized by the predominantapplication to a low power state or to a disabled power state, etc.),and context sensitive power recommendations (e.g., recommendation toconfigure the mobile device 102-1 to a low power state and charging themobile device 102-1 etc.).

FIG. 4A illustrates one embodiment of a logic flow 400. The logic flow400 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 4A, the logic flow 400 maystart at block 402 and may monitor one or more applications and/or oneor more components of a mobile device to determine device profileinformation at step 404. For example, power application 124-1-1 viapower monitoring component 190-3 may monitor one or more applicationand/or one or more components of the mobile device 102-1 by capturingand/or storing device application information 210-1, device componentinformation 210-2, device event information 210-3, and/or devicelocation information 210-4 to determine device profile information.

The logic flow 400 may provide the device profile information to aserver device at 406. For example, power application 124-1-1 via powercommunications component 190-5 may provide the device profileinformation to power analytics application 109 executing on serverdevice 106-2.

The logic flow 400 may receive predicted information and/or contextinformation at 408. For example, the power management component 190-1may receive predicted information (e.g., predicted power curveinformation 212-4, predicted context information 212-5, predicted powerevent information 212-7, etc.) and recommendation information (e.g.context sensitive recommendation information 212-6, etc.) from the poweranalytics application 109 of the power analysis system 105.

The logic flow 400 may present, visually, the received contextrecommendation and/or predicted information 410 and end at 412. Forexample, the power management component 190-1 may, via the powerrendering component 190-2, visually present the one or more contextsensitive recommendations (e.g., terminating one or more non-predominantapplications, configuring one or more applications to a low power state,configuring one or more components to a low power state, charging thebattery 188 of the mobile device, etc.) and/or one or more predictedpower curves represented by predicted power curve information. Theexamples are not limited in this context.

FIG. 4B illustrates one embodiment of a logic flow 450. The logic flow450 may be representative of some or all of the operations executed byone or more embodiments described herein.

In the illustrated embodiment shown in FIG. 4B, the logic flow 450 maystart at block 452 and receive device profile information from mobiledevice at 454. For example, the power analytics management component114-1 of power analytics application 109 in the power analysis systemmay receive, periodically, the device profile information (e.g., deviceapplication information 210-1, device component information 210-2,device event information 210-3, and/or device location information210-4, etc.) for mobile device 102-1.

The logic flow 450 may determine analytics information for mobile deviceat 456. For example, the power analytics management component 114-1 mayinitiate the determination of analytics information (e.g., analyticsmodel information 212-1, analytics power curve information 212-2,analytics context information 212-3, etc.) by the power analyticsmodeling component 114-2 for mobile device 102-1.

The logic flow 450 may determine predicted information andrecommendation information for the mobile device at 458. For example,the power analytics prediction component 114-3 may determine predictedinformation (e.g., predicted power curve information 212-4, predictedcontext information 212-5, predicted power event information 212-7,etc.) and recommendation information (e.g. context sensitiverecommendation information 212-6, etc.) based at least partially on theanalytics information and the device profile information.

The logic flow 450 may provide predicted information and/or therecommendation information to the mobile device 460 and end at 462. Forexample, the power analytics management component 114-1 may provide thepredicted information (e.g., predicted power curve information 212-4,predicted context information 212-5, predicted power event information212-7, etc.) and/or recommendation information (e.g. context sensitiverecommendation information 212-6, etc.) via the power analyticscommunications component 114-4 to the mobile power application 124-1-1of the mobile device 102-1. The examples are not limited in thiscontext.

FIG. 5 illustrates an embodiment of an exemplary computing architecture500 suitable for implementing various embodiments as previouslydescribed, such as, for example server device 106 and/or one or moredevices 102-a. In one embodiment, the computing architecture 500 maycomprise or be implemented as part of an electronic device. In anotherembodiment, the computer architecture 500 may be implemented as part ofa cloud computing platform as a physical machine or virtual machine in anetwork of one or more physical and/or virtual machines. The embodimentsare not limited in this context.

As used in this application, the terms “system” and “component” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution, examples of which are provided by the exemplary computingarchitecture 500. For example, a component can be, but is not limited tobeing, a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical and/or magnetic storage medium), anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution, and a component canbe localized on one computer and/or distributed between two or morecomputers. Further, components may be communicatively coupled to eachother by various types of communications media to coordinate operations.The coordination may involve the uni-directional or bi-directionalexchange of information. For instance, the components may communicateinformation in the form of signals communicated over the communicationsmedia. The information can be implemented as signals allocated tovarious signal lines. In such allocations, each message is a signal.Further embodiments, however, may alternatively employ data messages.Such data messages may be sent across various connections. Exemplaryconnections include parallel interfaces, serial interfaces, and businterfaces.

The computing architecture 500 includes various common computingelements, such as one or more processors, multi-core processors,co-processors, memory units, chipsets, controllers, peripherals,interfaces, oscillators, timing devices, video cards, audio cards,multimedia input/output (I/O) components, power supplies, and so forth.The embodiments, however, are not limited to implementation by thecomputing architecture 500.

As shown in FIG. 5, the computing architecture 500 comprises aprocessing unit 504, a system memory 506 and a system bus 508. Theprocessing unit 504 can be any of various commercially availableprocessors, including without limitation an AMD® Athlon®, Duron® andOpteron® processors; ARM® application, embedded and secure processors;IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony®Cell processors; Intel® Celeron®, Core (2) Duo®, Itanium®, Pentium®,Xeon®, and XScale® processors; and similar processors. Dualmicroprocessors, multi-core processors, and other multi-processorarchitectures may also be employed as the processing unit 504.

The system bus 508 provides an interface for system componentsincluding, but not limited to, the system memory 506 to the processingunit 504. The system bus 508 can be any of several types of busstructure that may further interconnect to a memory bus (with or withouta memory controller), a peripheral bus, and a local bus using any of avariety of commercially available bus architectures. Interface adaptersmay connect to the system bus 508 via a slot architecture. Example slotarchitectures may include without limitation Accelerated Graphics Port(AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA),Micro Channel Architecture (MCA), NuBus, Peripheral ComponentInterconnect (Extended) (PCI(X)), PCI Express, Personal Computer MemoryCard International Association (PCMCIA), and the like.

The computing architecture 500 may comprise or implement variousarticles of manufacture. An article of manufacture may comprise acomputer-readable storage medium to store logic. Examples of acomputer-readable storage medium may include any tangible media capableof storing electronic data, including volatile memory or non-volatilememory, removable or non-removable memory, erasable or non-erasablememory, writeable or re-writeable memory, and so forth. Examples oflogic may include executable computer program instructions implementedusing any suitable type of code, such as source code, compiled code,interpreted code, executable code, static code, dynamic code,object-oriented code, visual code, and the like. Embodiments may also beat least partly implemented as instructions contained in or on anon-transitory computer-readable medium, which may be read and executedby one or more processors to enable performance of the operationsdescribed herein.

The system memory 506 may include various types of computer-readablestorage media in the form of one or more higher speed memory units, suchas read-only memory (ROM), random-access memory (RAM), dynamic RAM(DRAM), Double-Data-Rate DRAM (DDRAM), synchronous DRAM (SDRAM), staticRAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM),electrically erasable programmable ROM (EEPROM), flash memory, polymermemory such as ferroelectric polymer memory, ovonic memory, phase changeor ferroelectric memory, silicon-oxide-nitride-oxide-silicon (SONOS)memory, magnetic or optical cards, an array of devices such as RedundantArray of Independent Disks (RAID) drives, solid state memory devices(e.g., USB memory, solid state drives (SSD) and any other type ofstorage media suitable for storing information. In the illustratedembodiment shown in FIG. 5, the system memory 506 can includenon-volatile memory 510 and/or volatile memory 512. A basic input/outputsystem (BIOS) can be stored in the non-volatile memory 510.

The computer 502 may include various types of computer-readable storagemedia in the form of one or more lower speed memory units, including aninternal (or external) hard disk drive (HDD) 514, a magnetic floppy diskdrive (FDD) 516 to read from or write to a removable magnetic disk 518,and an optical disk drive 520 to read from or write to a removableoptical disk 522 (e.g., a CD-ROM or DVD). The HDD 514, FDD 516 andoptical disk drive 520 can be connected to the system bus 508 by a HDDinterface 524, an FDD interface 526 and an optical drive interface 528,respectively. The HDD interface 524 for external drive implementationscan include at least one or both of Universal Serial Bus (USB) and IEEE1394 interface technologies.

The drives and associated computer-readable media provide volatileand/or nonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For example, a number of program modules canbe stored in the drives and memory units 510, 512, including anoperating system 530, one or more application programs 532, otherprogram modules 534, and program data 536. In one embodiment, the one ormore application programs 532, other program modules 534, and programdata 536 can include, for example, the various applications and/orcomponents of the system 100.

A user can enter commands and information into the computer 502 throughone or more wire/wireless input devices, for example, a keyboard 538 anda pointing device, such as a mouse 540. Other input devices may includemicrophones, infra-red (IR) remote controls, radio-frequency (RF) remotecontrols, game pads, stylus pens, card readers, dongles, finger printreaders, gloves, graphics tablets, joysticks, keyboards, retina readers,touch screens (e.g., capacitive, resistive, etc.), trackballs,trackpads, sensors, styluses, and the like. These and other inputdevices are often connected to the processing unit 504 through an inputdevice interface 542 that is coupled to the system bus 508, but can beconnected by other interfaces such as a parallel port, IEEE 1394 serialport, a game port, a USB port, an IR interface, and so forth.

A monitor 544 or other type of display device is also connected to thesystem bus 508 via an interface, such as a video adaptor 546. Themonitor 544 may be internal or external to the computer 502. In additionto the monitor 544, a computer typically includes other peripheraloutput devices, such as speakers, printers, and so forth.

The computer 502 may operate in a networked environment using logicalconnections via wire and/or wireless communications to one or moreremote computers, such as a remote computer 548. The remote computer 548can be a workstation, a server computer, a router, a personal computer,portable computer, microprocessor-based entertainment appliance, a peerdevice or other common network node, and typically includes many or allof the elements described relative to the computer 502, although, forpurposes of brevity, only a memory/storage device 550 is illustrated.The logical connections depicted include wire/wireless connectivity to alocal area network (LAN) 552 and/or larger networks, for example, a widearea network (WAN) 554. Such LAN and WAN networking environments arecommonplace in offices and companies, and facilitate enterprise-widecomputer networks, such as intranets, all of which may connect to aglobal communications network, for example, the Internet.

When used in a LAN networking environment, the computer 502 is connectedto the LAN 552 through a wire and/or wireless communication networkinterface or adaptor 556. The adaptor 556 can facilitate wire and/orwireless communications to the LAN 552, which may also include awireless access point disposed thereon for communicating with thewireless functionality of the adaptor 556.

When used in a WAN networking environment, the computer 502 can includea modem 558, or is connected to a communications server on the WAN 554,or has other means for establishing communications over the WAN 554,such as by way of the Internet. The modem 558, which can be internal orexternal and a wire and/or wireless device, connects to the system bus508 via the input device interface 542. In a networked environment,program modules depicted relative to the computer 502, or portionsthereof, can be stored in the remote memory/storage device 550. It willbe appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computerscan be used.

The computer 502 is operable to communicate with wire and wirelessdevices or entities using the IEEE 802 family of standards, such aswireless devices operatively disposed in wireless communication (e.g.,IEEE 802.11 over-the-air modulation techniques). This includes at leastWi-Fi (or Wireless Fidelity), WiMax, and BluetoothTM wirelesstechnologies, among others. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.11x (a, b, g, n, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

Some embodiments may be described using the expression “one embodiment”or “an embodiment” along with their derivatives. These terms mean that aparticular feature, structure, or characteristic described in connectionwith the embodiment is included in at least one embodiment. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment.Further, some embodiments may be described using the expression“coupled” and “connected” along with their derivatives. These terms arenot necessarily intended as synonyms for each other. For example, someembodiments may be described using the terms “connected” and/or“coupled” to indicate that two or more elements are in direct physicalor electrical contact with each other. The term “coupled,” however, mayalso mean that two or more elements are not in direct contact with eachother, but yet still co-operate or interact with each other.

It is emphasized that the Abstract of the Disclosure is provided toallow a reader to quickly ascertain the nature of the technicaldisclosure. It is submitted with the understanding that it will not beused to interpret or limit the scope or meaning of the claims. Inaddition, in the foregoing Detailed Description, it can be seen thatvarious features are grouped together in a single embodiment for thepurpose of streamlining the disclosure. This method of disclosure is notto be interpreted as reflecting an intention that the claimedembodiments need more features than are expressly recited in each claim.Rather, as the following claims reflect, inventive subject matter liesin less than all features of a single disclosed embodiment. Thus thefollowing claims are hereby incorporated into the Detailed Description,with each claim standing on its own as a separate embodiment. In theappended claims, the terms “including” and “in which” are used as theplain-English equivalents of the respective terms “comprising” and“wherein,” respectively. Moreover, the terms “first,” “second,” “third,”and so forth, are used merely as labels, and are not intended to imposenumerical requirements on their objects.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.

1. A computer-implemented method, comprising: monitoring one or more ofa component or an application of a mobile device to determine deviceprofile information of a mobile device; transmitting the determineddevice profile information to a server device; and receiving predictedinformation representative of one or more of forecasted powerutilization of the mobile device or context sensitive recommendationinformation representative of one or more context sensitiverecommendations for the mobile device, wherein the predicted informationor the context sensitive recommendation information is determined basedat least partially on the device profile information of the mobiledevice.
 2. The computer-implemented method of claim 1, wherein thedevice profile information further comprises one or more of deviceapplication information, device component information, device eventinformation, or device location information, and the predictedinformation further comprises predicted context information, andpredicted power event information.
 3. The computer-implemented method ofclaim 1, wherein the predicted information comprises predicted powercurve information generated based at least partially on one or more offuture power curve information, past power curve information, oranalytics power curve information.
 4. The computer-implemented method ofclaim 3, wherein the future power curve information is generated basedat least partially on a corresponding future location contextinformation representing one or more of scheduled locations associatedwith the mobile device or corresponding future event context informationrepresentative of future event contexts that identify at least onescheduled device event.
 5. The computer-implemented method of claim 1,further comprising: presenting context sensitive recommendationinformation representative of at least one context sensitiverecommendation on a display screen of the mobile device, the at leastone context sensitive recommendation comprising a first contextsensitive recommendation for reducing power utilization of the mobiledevice based at least partially on one or more of a correspondinganalytics context or a future context.
 6. The computer-implementedmethod of claim 5, wherein the at least one context sensitiverecommendation comprises one or more of a context sensitive applicationrecommendation, a context sensitive component recommendation, or acontext sensitive power recommendation.
 7. The computer-implementedmethod of claim 1, wherein the device profile information is provided tothe server device on a predefined interval.
 8. A non-transitorycomputer-readable medium storing instructions that, when executed by aprocessor, cause the processor to: monitor one or more of a component oran application of a mobile device to determine device profileinformation of a mobile device; transmit the determined device profileinformation to a server device; and receive predicted informationrepresentative of one or more of forecasted power utilization of themobile device or context sensitive recommendation informationrepresentative of one or more context sensitive recommendations for themobile device, wherein the predicted information or the contextsensitive recommendation information is determined based at leastpartially on the device profile information of the mobile device.
 9. Themedium of claim 8, wherein the device profile information furthercomprises one or more of device application information, devicecomponent information, device event information, or device locationinformation, and the predicted information further comprises predictedcontext information, and predicted power event information.
 10. Themedium of claim 8, wherein the predicted information comprises predictedpower curve information generated based at least partially on one ormore of future power curve information, past power curve information, oranalytics power curve information.
 11. The medium of claim 10, whereinthe future power curve information is generated based at least partiallyon a corresponding future location context information representing oneor more of scheduled locations associated with the mobile device orcorresponding future event context information representative of futureevent contexts that identify at least one scheduled device event. 12.The medium of claim 8, further storing instructions for: presentingcontext sensitive recommendation information representative of at leastone context sensitive recommendation on a display screen of the mobiledevice, the at least one context sensitive recommendation comprising afirst context sensitive recommendation for reducing power utilization ofthe mobile device based at least partially on one or more of acorresponding analytics context or a future context.
 13. The medium ofclaim 12, wherein the at least one context sensitive recommendationcomprises one or more of a context sensitive application recommendation,a context sensitive component recommendation, or a context sensitivepower recommendation.
 14. An apparatus, comprising: a processor circuit;memory operatively coupled to the processor circuit, the memory to storea mobile power application for execution by the processor circuit, themobile power application comprising a power monitoring component tomonitor one or more of a component or an application of a mobile deviceto determine device profile information of a mobile device; a powermanagement component configured to provide the determined device profileinformation to a server device and receive predicted informationrepresentative of one or more of forecasted power utilization of themobile device or context sensitive recommendation informationrepresentative of one or more context sensitive recommendations for themobile device, wherein the predicted information or the contextsensitive recommendation information is determined based at leastpartially on the device profile information of the mobile device. 15.The apparatus for claim 14, wherein the device profile informationfurther comprises one or more of device application information, devicecomponent information, device event information, or device locationinformation, and the predicted information comprises predicted contextinformation, and predicted power event information.
 16. Thecomputer-implemented method of claim 14, wherein the predictedinformation comprises predicted power curve information generated basedat least partially on one or more of past power curve information oranalytics power curve information.
 17. The apparatus for claim 14,wherein the predicted information comprises future power curveinformation generated based at least partially on device applicationevent information.
 18. The apparatus for claim 14, wherein the predictedinformation comprises future power curve information generated based atleast partially on analytics model information for other mobile devices,and the application has not been previously executed by the mobiledevice.
 19. The apparatus of claim 18, wherein the mobile device isassociated with a user, and the processor circuit is configured tosocially connect the user to other users of a social networking systembased at least partially on user profile information associated with theuser and the other users.
 20. The apparatus of claim 14, furthercomprising a display configured to present, visually, context sensitiverecommendation information representative of at least one contextsensitive recommendation, the at least one context sensitiverecommendation comprising a recommendation for reducing powerutilization of the mobile device based at least partially on one or moreof a corresponding analytics context or future context.